Best practices for tagging on branches

[Arne Babenhauserheide]

Am Dienstag 28 April 2009 16:35:24 schrieb Greg Ward:
> I think this just means that any strict tagging policies need to be
> configurable, and the default policy should be the status quo.  (Hmmm:
> would it be possible to implement such tagging policies in hooks?
> That would be the ideal place for various projects to experiment and
> come up with guidelines like "this policy works great" or "this is a
> dumb policy -- don't do it".)

Can a preincoming hook do this? If a changeset modified .hgtags and is not on 
the default branch, don't allow the push/pull. 

Best wishes, 
Arne

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- 
   - singing a part of the history of free software -
              http://infinite-hands.draketo.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20090428/4bace71e/attachment.pgp