[RFC] Enforcing a "linear" repository by first parent?

0000 vk 0000.vk at gmail.com
Thu Mar 19 14:43:44 CDT 2009


On Thu, Mar 19, 2009 at 3:31 PM, Ted Pavlic <ted at tedpavlic.com> wrote:
>> Less smart-alecky response: embrace the brave new world.  Branches and
>> merges happen all the time, so why not let your history reflect that?
>> Use rebase if you don't want so many silly little merge changesets.
>
> You could even put (in ~/.hgrc or the repo-specific hgrc's)...
>
> [defaults]
> pull = --rebase
>
> [extensions]
> hgext.rebase =
>
> Then tell everyone to do an "hg pull" before every push. That should go
> a long way to getting rid of un-meaningful merges (and it still allows
> for meaningful merges),
>
> --Ted
>
> --
> Ted Pavlic <ted at tedpavlic.com>

yeah. or you could have a gatekeeper to that tree, and only accept
patches. this will force the committers to rebase against that tree.
would that work?



More information about the Mercurial mailing list