How to deal with command restrictions (strip/revert)

heimi andreas.heidrich at gmail.com
Thu May 27 15:35:31 UTC 2010


We evaluate Hg currently. We use CVS today and we would like to switch
to a modern SCM now.

I looked all over the selenic side with tons of documentation, but
found nowhere information reg this question/szenario:

We would like to use a central repo as push target for all developers.
When we reach a release state, we would like to "fix" this part of the
repository and would like to restrict the use of revert or strip
commands because this production level code should never be changed
aftherwards.

I cannot see a way to restrict any of these "critical" commands.

Can anyone give me a hint how we can solve this, Either by a command /
Extension or by a hint how to deal with this situation in a DSCM -
Way ?

Thanx in advance
Andreas



More information about the Mercurial mailing list