hg-git and git tags handling

Augie Fackler durin42 at gmail.com
Mon Jul 20 10:42:21 CDT 2009

On Jul 20, 2009, at 10:22 AM, Abderrahim Kitouni wrote:

> 2009/7/20 Augie Fackler <durin42 at gmail.com>:
>> I'm not as familiar as I'd like with Git's handling of tags - are  
>> they
>> supposed to not change as in the usual tools won't let you without a
>> --force, or they aren't supposed to change merely by convention of  
>> them
>> being tags?
> git tag won't let you change a tag without a --force, a git pull won't
> pull any existing tags, even if they changed. (you need to delete the
> tag and pull again)
>> If the former, then maybe we can do something with the  
>> actual .hgtags file
>> in an unrelated branch that gets saved in the repo, but that feels  
>> a bit
>> messy to me.
> I also thought about this, especially for annotated tags (they contain
> a committer, a date, and can contain a gpg signature), but as you say,
> this feels messy. we should make sure that the new branch doesn't get
> in the way.

Could we mask the branch from the user somehow? After all, we're  
already subclassing the repository.

I don't really know how I feel about that implementation-wise, can  
others comment with their feelings on such a hack?

> Abderrahim

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2417 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial-devel/attachments/20090720/3dbd79b9/attachment.bin 

More information about the Mercurial-devel mailing list