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

Re: [PATCH] rev-list: heed --abbrev-commit option

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Mar 27, 2010, 13:30 UTC
Message-ID
<4BAE0874.6090603@drmicha.warpmail.net>
In-Reply-To
<7vk4sylvzj.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 26.03.2010 20:32:
Show 13 quoted lines
> Michael J Gruber <git@drmicha.warpmail.net> writes:
> 
>> Currently, rev-list has a default of "0" for abbrev which means that
>> switching on abbreviations with --abbrev-commit has no visible effect,
>> even though the option is documented.
> 
> Hmm, I actually think this was deliberate.  rev-list is designed to be a
> low level machinery for getting full object names, and in that context,
> setting the default abbreviation length to "don't abbreviate" gave us some
> safety, with additional safety of requiring a separate --abbrev-commit
> option to affect the main "show the commit object names" codepath (the
> latter of which would not likely to change).  The caller sets explicitly
> how long an output it wants (see git-rebase--interactive for an example).

My thinking was that unless --abbrev-commit is specified, nothing is abbreviated, so that one has reproducible (plumbing) behaviour.

I learned that --abbrev= implies --abbrev-commit, but again, this means explicitly requiring non-plumbing behavior.

> 
> Having said that, I don't think this would break existing scripts, so
> let's queue it and see what happens.

OK! Michael

Previous: Junio C HamanoNext: Eli Barzilay
Message 6 of 14 in “git rev-list formatting”
  1. Eli BarzilayMar 22, 2010
  2. Eli BarzilayMar 22, 2010
  3. Michael J GruberMar 22, 2010
  4. rev-list: heed --abbrev-commit optionMichael J Gruber, Mar 22, 2010
  5. Junio C HamanoMar 26, 2010
  6. Michael J GruberMar 27, 2010
  7. Eli BarzilayMar 22, 2010
  8. René ScharfeMar 22, 2010
  9. Eli BarzilayMar 23, 2010
  10. Michael J GruberMar 23, 2010
  11. Eli BarzilayMar 23, 2010
  12. Jeff KingMar 23, 2010
  13. Erik Faye-LundMar 23, 2010
  14. Eli BarzilayMar 23, 2010

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.