git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH] GIT-VERSION-GEN: set --abbrev=9 to match auto-scaling

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 5, 2016, 18:01 UTC
Message-ID
<xmqqbmwq5k7k.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20161205053258.jtnqq64gp5n7vtni@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 29 quoted lines
> On Sun, Dec 04, 2016 at 08:45:59PM +0000, Ramsay Jones wrote:
>
>> 
>> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
>> ---
>> 
>> Hi Junio,
>> 
>> I recently noticed that:
>> 
>>     $ make >pout 2>&1
>>     $ ./git version
>>     git version 2.11.0.286.g109e8a9
>>     $ git describe
>>     v2.11.0-286-g109e8a99d
>>     $
>> 
>> ... for non-release builds, the commit part of the version
>> string was still using an --abbrev=7.
>
> It seems like this kind of discussion ought to go in the commit message.
> :)
>
> That said, I think the right patch may be to just drop --abbrev
> entirely.
> ...
> I think at that point it was a noop, as 7 should have been the default.
> And now we probably ought to drop it, so that we can use the
> auto-scaling default.
Yeah, I agree.

It does mean that snapshot binaries built out of the same commit in the same repository before and after a repack have higher chances of getting named differently, which may surprise people, but that already is possible with a fixed length if the repacking involves pruning (albeit with lower probabilities), and I do not think it is a problem.

Previous: Ramsay JonesNext: Jeff King
Message 8 of 12 in “GIT-VERSION-GEN: set --abbrev=9 to match auto-scaling”
  1. GIT-VERSION-GEN: set --abbrev=9 to match auto-scalingRamsay Jones, Dec 4, 2016
  2. Jeff KingDec 5, 2016
  3. Ramsay JonesDec 5, 2016
  4. Junio C HamanoDec 5, 2016
  5. Ramsay JonesDec 5, 2016
  6. Junio C HamanoDec 5, 2016
  7. Ramsay JonesDec 5, 2016
  8. Junio C HamanoDec 5, 2016
  9. Jeff KingDec 6, 2016
  10. Junio C HamanoDec 6, 2016
  11. Jeff KingDec 6, 2016
  12. Ramsay JonesDec 6, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.