.hgtags not cloned
Sebastian Hauer
sebastian.hauer at gmail.com
Fri Oct 19 12:58:23 CDT 2007
Hi Lars,
On 10/18/07, Lars Wilke <lw at lwilke.de> wrote:
> * Dustin Sallings wrote:
> > On Oct 16, 2007, at 8:10 , Sebastian Hauer wrote:
> > > I just noticed that .hgtags does not necessarily get cloned when I do
> > > the following:
...
> > This gets all changesets defined within the tag, but not the tag
> > itself. The tag is a subsequent changeset.
>
> Could hg not just do a second autmatic commit, so that one only needs to
> point to that revision. The current behaviour is IMHO not very intuitive
> and confuses me once in a while :)
Not sure how the auto-commit thing would work with the revisions (e.g.
what happens if you tag an older revision) but I think the
problem/confusion is with the current design. Although I like it for
its simplicity (all tags versioned in a simple .hgtags text file) but
I agree with you that it is not very intuitive. Perhaps tags should
be stored as part of the meta information under Project/.hg/ so that
one can clone them even if one is just cloning based on a tag and the
full tag information exists in the cloned repo.
Regards,
Sebastian
More information about the Mercurial
mailing list