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

Re: [RFC PATCH] rev-list: clarify --abbrev and --abbrev-commit usage

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 14, 2019, 16:09 UTC
Message-ID
<xmqq8su4up14.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<20190613221541.10007-1-emilyshaffer@google.com>
Emily Shaffer <emilyshaffer@google.com> writes:
> It looks like `git log --abbrev=5` also doesn't work the way one might
> expect, which makes sense to me, as they use the same internals for
> option parsing (parse_revisions()).

I suspect that was primarily because --abbrev-commit was only to abbreviate the commit object names on the log header, and --abbrev was to abbreviate the object names seen in the --raw output. These days, even --raw output seems to abbreviate by default, so --abbrev alone lost its usefulness quite a bit.

Previous: Emily ShafferNext: Jeff King
Message 2 of 8 in “rev-list: clarify --abbrev and --abbrev-commit usage”
  1. rev-list: clarify --abbrev and --abbrev-commit usageEmily Shaffer, Jun 13, 2019
  2. Junio C HamanoJun 14, 2019
  3. Jeff KingJun 14, 2019
  4. Emily ShafferJun 14, 2019
  5. Jeff KingJun 14, 2019
  6. Emily ShafferJun 14, 2019
  7. Jeff KingJun 19, 2019
  8. Emily ShafferJun 19, 2019

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.