Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!news.linkpendium.com!news.linkpendium.com!newsfeeds.ihug.co.nz!lust.ihug.co.nz!ihug.co.nz!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.lang.java.programmer Subject: Re: git-describe Followup-To: comp.lang.java.programmer Date: Fri, 27 May 2011 11:00:38 +1200 Organization: Geek Central Lines: 28 Message-ID: References: NNTP-Posting-Host: 118-92-95-178.dsl.dyn.ihug.co.nz Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8Bit X-Trace: lust.ihug.co.nz 1306450838 5443 118.92.95.178 (26 May 2011 23:00:38 GMT) X-Complaints-To: abuse@ihug.co.nz NNTP-Posting-Date: Thu, 26 May 2011 23:00:38 +0000 (UTC) User-Agent: KNode/4.4.7 Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4617 In message , Tom Anderson wrote: > The problem with this is that the numbers record the sequence in which > changesets were added to the current repository - which in the presence of > commits on multiple machines (ie for any realistic development team) means > that the numbers won't be the same in different repositories. Sounds like it’s more equivalent to what you might get out of a “reflog” on Git. This is a purely personal, interim record of changes to the repository, which is never pushed/pulled as part of the repository itself, and can be purged (on demand) at any time. > Mercurial has a very slight edge here, in that as well as the hash-based > changeset IDs, it also has a sequential changeset number. As soon as I read this, I wondered what would happen to the numbering if you did the Git equivalent of committing something, then abandoning that commit (resetting that branch back to a prior commit) and making a new one. This can’t just arise from mistakes; it’s recommended in the Git docs as a handy way of saving temporary changes while working om something else. >> Exercise for the reader: what happens if you don’t specify “--tags”? > > States it as revisions from the initial checkin? Actually, no. It turns out there are two different kinds of tags, and which one is used depends on this option.