Re: Remote git-describe ?
- From
- Santi Béjar <sbejar@gmail.com>
- Date
- Jan 24, 2007, 13:01 UTC
- Message-ID
- <8aa486160701240501t3f6919b0tcd19da131a196dbb@mail.gmail.com>
- In-Reply-To
- <7vlkjsfvro.fsf@assigned-by-dhcp.cox.net>
On 1/24/07, Junio C Hamano <junkio@cox.net> wrote:
Show 17 quoted lines
> Also the commit object names (hence "describe" output) do not > tell you how far they are from the tag used to describe them. > > However, I suspect that we could do better with Shawn's new > fangled describe implementation that actually counts the > distance between what is described and the tag. We could add > "number of commits since the tag" somewhere, to describe: > > v2.6.20-rc5-256-g419dd83 > v2.6.20-rc5-217-gde14569 > > to say that the first one has 256 commits accumulated since the > given tag "v2.6.20-rc5" and the second one has only 217 > commits, to get the sense of how busy the development activity > is. > > Is it useful? That is something I am not sure.
I find it usefull. I even suggested it in November: http://marc.theaimsgroup.com/?l=git&m=116246596012422&w=2
Quote: One problem I see with this scheme (either 'g', 'git' of '+') is that it does not provide an increasing version number, even for fast-forwarding commits. Then it is not useful as a package version number (deb or rpm). I've already seen deb packages with version+git20061010. End Quote:
The "either 'g',..." was something it that thread, but applies to the current scheme.
Santi
Show 15 quoted lines
> > Side note for side note. > > This should be obvious to people who know git, but the above > does not mean we can remove gXXXX part from the describe output, > becauses there could be infinite number of commits that are 256 > commits away from v2.6.20-rc5 tag. v2.6.20-rc5-256 alone does > not uniquely identify the commit 419dd83. > > > - > To unsubscribe from this list: send the line "unsubscribe git" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html >