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

git-blame vs. abbrev

From
LELaszlo Ersek <laszlo.ersek@posteo.net>
Date
Jun 30, 2026, 11:15 UTC
Message-ID
<b500479b-14c1-4fbb-a672-1d2cd4852601@posteo.net>
Hi,

when git-blame is passed the "-b" option ("Show blank SHA-1 for boundary commits"), shouldn't git-blame *stop* reserving a commit hash nibble for the caret that otherwise marks boundary commits?

More directly, I find it inconvenient that git-blame shows commit hashes that are one nibble longer (13) than my "core.abbrev" (12) setting; that makes cutting and pasting commit hashes from the git-blame output into a git-rebase TODO list cumbersome. I briefly hoped that by setting "blame.blankBoundary", I could get around that, but it doesn't seem to work (I tried with Git 2.55). I now have an alias that passes "--abbrev=11" explicitly, as a last resort, to git-blame. (Even a potential "blame.abbrev" would be superior, but such a permanent setting doesn't seem to exist.)

Thanks, Laszlo Ersek

Next: Junio C Hamano
Message 1 of 9 in “git-blame vs. abbrev”
  1. Laszlo ErsekJun 30, 2026
  2. Junio C HamanoJun 30, 2026
  3. Laszlo ErsekJun 30, 2026
  4. Junio C HamanoJun 30, 2026
  5. Laszlo ErsekJul 1, 2026
  6. René ScharfeJun 30, 2026
  7. Laszlo ErsekJul 1, 2026
  8. blame: reserve mark column only if necessaryRené Scharfe, Jul 6, 2026
  9. Junio C HamanoJul 6, 2026

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.