[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#15696: 24.3; vc-git-annotate-command -- ambiguous short commit hashe
From: |
Lars Ingebrigtsen |
Subject: |
bug#15696: 24.3; vc-git-annotate-command -- ambiguous short commit hashes cause failures |
Date: |
Sun, 06 Dec 2020 16:17:52 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
"Phil Sainty" <psainty@orcon.net.nz> writes:
> `vc-git-annotate-command' looks like this:
>
> (defun vc-git-annotate-command (file buf &optional rev)
> (let ((name (file-relative-name file)))
> (vc-git-command buf 'async nil "blame" "--date=iso" "-C" "-C" rev "--"
> name)))
>
> By default, git blame produces short commit hashes. You need to pass
> the -l argument to make it produce full hashes.
>
> This is a problem if the short hash is ambiguous, as none of the
> vc-annotate commands for interacting with that commit work.
>
> Example errors for ambiguous commit hash 7b10edf8:
(This bug report unfortunately got no response at the time.)
The command in question now produces an 11-char short hash, which I
think is pretty rarely ambiguous, in my experience, so I don't think
there's anything more to fix here, and I'm closing this bug report.
If there's still a problem here, please respond to the debbugs address
and we'll reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#15696: 24.3; vc-git-annotate-command -- ambiguous short commit hashes cause failures,
Lars Ingebrigtsen <=