Best practices for tagging on branches

[L. David Baron]

On Monday 2009-04-27 20:56 +0200, Dirkjan Ochtman wrote:
> I've thought that it might be worthwhile to forbid tagging changesets  
> that where ancestor(tagging, tagged) != tagged, i.e. the tagging  
> changeset must be a child of the tagged changeset. Not doing so caused  
> some problems for some guy a while back. Not sure that comes down to the  
> same rules you're proposing, though.

That's different from what I'm proposing.

It avoids a different problem -- one that I've also seen -- where a
pulling part of a repository (e.g., with -r) leads to many hg
commands failing due to the inconsistency of the tag state, since
some tags refer to revisions that don't exist.

I have no idea how to avoid both problems.

-David

-- 
L. David Baron                                 http://dbaron.org/
Mozilla Corporation                       http://www.mozilla.com/