Thursday, 15 August 2013

repository - Mercurial: Multiple commit histories -



repository - Mercurial: Multiple commit histories -

we collaborate 3rd party (contractor) using our "master" mercurial repo on project client. appears cluttered commit history (including trail , errors). we'd hide these details client (i.e. not reveal whole commit history). however, @ same time, utilize repo deliver our results client (in orderly , more "condensed" form). there recommend work flow (and tooling/hg commands) suit purpose?

there's no good/easy way this, there plenty of bad/hard ways it. here few:

internally work in mecurial queues , qfinish changesets when done / perfect. give them access repo not mq repo (they're optionally, separately versioned)

use things rewrite history commit --ammend or histedit's collapse command alter repo after (drawback, on team has delete , reclone)

create totally separate repo them , when you're ready give them drop re-create in hg archive repo , commit

i don't think of worth hassle of hiding normal software development work, there go.

mercurial repository revision-history

No comments:

Post a Comment