Re: git-describe
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--232016332-1012980313-1306625131=:28130
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8BIT
On Sat, 28 May 2011, Lawrence D'Oliveiro wrote:
In message <alpine.DEB.2.00.1105272251580.1610@urchin.earth.li>, Tom
Anderson wrote:
It's also the normal way of working in Mercurial (as long as 'resetting'
doesn't mean 'throwing away').
In Git, ???resetting??? does indeed mean ???throwing away???.
Okay. In that case, the equivalent would actually be a little dance
involving hg clone - Mercurial makes it much harder to throw things away -
and the numbering would be reset, in a manner of speaking, since the clone
would create a new numbering.
Here's a brief session that illustrates what happens:
$ hg update 0
So this command has started a new branch?
No, but a branch was created when i committed after that.
In Git, every branch has a name.
Not so in Mercurial. This is, famously, one of the areas of greatest
difference between Git and Mercurial - Mercurial can have completely
anonymous branches, which it seems Git can't, but when it does have named
branches, it brands the name onto each changeset in it, which Git doesn't.
And what Git calls branches, Mercurial calls bookmarks, etc, etc.
AIUI, the reason anonymous branches don't exist in Git is because (a)
there would be no way to get to them (apart from reflog!) and (b) they
would get garbage collected, because names function as the rootset for
garbage collection. Mercurial doesn't do garbage collection (er, i think),
so you can have anonymous branches. The lack of names does obviously mean
that their utility is rather limited in scope.
Actually, no. It turns out there are two different kinds of tags, and
which one is used depends on this option.
That's the kind of thing that's the reason i don't use git.
This is why you need to understand things before trying to rubbish them.
Something i am very happy to say it has never been my policy to do.
tom
--
The ``is'' keyword binds with the same precedence as ``.'', even when
it's not actually there. -- Larry Wall, Apocalypse 2
--232016332-1012980313-1306625131=:28130--