Disable backing out merges?

Didly didlybom at gmail.com
Tue Oct 11 01:54:55 CDT 2011


On Tue, Oct 11, 2011 at 2:03 AM, Greg Ward <greg-hg at gerg.ca> wrote:
> On Fri, Oct 7, 2011 at 2:07 AM, Didly <didlybom at gmail.com> wrote:
>> could you give more details about your "mechanism to control everyone's .hgrc"?
>>
>> As the person unofficially in charge of mercurial at my company, this
>> is something that I wish was built-in into mercurial (perhaps as an
>> extension).
>
> Sure: it's called clonerc, and I've attached the source. Should be
> self-explanatory. Enjoy!
>
> Greg
>

Thank you Greg!

Your approach is interesting. I've been also looking at Martin's
solution (he made a somewhat similar extension, called Projrc,
http://mercurial.selenic.com/wiki/ProjrcExtension).

It seems that you overwrite the user's hgrc while Martin's solution
creats an extra "rc" file whose contents are read before reading the
repository's hgrc file. You also track this extra hgrc file, while
Martin's extension does not.

Cheers,

Angel


More information about the Mercurial-devel mailing list