Disable backing out merges?

Dan Villiom Podlaski Christiansen danchr at gmail.com
Fri Oct 7 11:05:34 CDT 2011


On 7 Oct 2011, at 09:08, Martin Geisler wrote:

> Didly <didlybom at gmail.com> writes:
> 
>> Greg,
>> 
>> 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).
> 
> There is such an extension:
> 
>  http://mercurial.selenic.com/wiki/ProjrcExtension
> 
> It lets you "radiate" options from a central repository to the clones.
> It's been used in production some time now at a client of mine.

Here's an idea for you: make the extension advertise a capability to say that it's enabled, and allow the administrator to require this capability. Then, if a user attempts to interact with (or merely push to) the central repository without this extension, they'll get an error.

(Just thinking out loud here; my employer hasn't even adopted Mercurial…)

--

Dan Villiom Podlaski Christiansen
danchr at gmail.com (mail & IM)



More information about the Mercurial-devel mailing list