Re: newbie questions about git design and features (some wrt hg)

From: Brendan Cully <brendan@kublai.com>
Date: Feb 3, 2007, 20:06 UTC
Message-ID: <20070203200638.GA6888@xanadu.kublai.com>
In-Reply-To: <200702022056.32791.jnareb@gmail.com>

On Friday, 02 February 2007 at 20:56, Jakub Narebski wrote:

> For example you are on branch 'master', you tag current release
> e.g. v1.3.4, then you checkout branch 'devel'... and you don't have
> v1.3.4 tag available unless you merge in .hgtags from 'master'.
> At least from what I understand of Mercurial tags behaviour.

This would be bad, if it were true.

$ hg up devel 2 files updated, 0 files merged, 0 files removed, 0 files unresolved $ cat .hgtags 6acda9aa5d8c621b3db2f2daab878d8de726d227 base $ hg tags tip 4:b1f003583d8e v1.3.4 2:87e43e86318f base 0:6acda9aa5d8c

As mentioned before, hg has local tags which sound an awful lot like git tags. It also has properly versioned tags. And, by the way, if you push a branch, you only push the tags that were committed on that branch. Furthermore, you can push based on a tag name that isn't committed in the branch you're pushing. I think the "globally global" nonsense elsewhere in this thread may be a result of not understanding this.

I'm probably done with this thread too. There's too much ignorant speculation to make it very productive.