Access control - author authenticity using a shared integration repository
Stanimir Stamenkov
s7an10 at netscape.net
Sun Jan 3 14:08:19 CST 2010
Wed, 30 Dec 2009 09:37:22 +0100, /Andreas Tscharner/:
> That depends on how these developers on that specific task work
> together. If they commit their part of the task to their repositories
> and share their repositories (using "hg serve" or the "Web server"
> command in TortoiseHG), all changesets (not only one) is pushed and the
> credits/submitter informations will be preserved. This works of course
> only if they work together in the described way and do not use the
> collapse extension or histedit extension
We'll probably use the collapse and/or histedit extensions but I
don't think the other way round would prevent someone from creating
a changeset titling it using author different from himself, also.
Given there could be lot of commits to the integration repo one
could easily miss he is pulling something from "himself" in the bulk.
--
Stanimir
More information about the Mercurial
mailing list