git-blame vs. abbrev

[Laszlo Ersek <laszlo.ersek@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