diff options
| author | Tom Ryder <tom@sanctum.geek.nz> | 2016-09-07 16:10:30 +1200 |
|---|---|---|
| committer | Tom Ryder <tom@sanctum.geek.nz> | 2016-09-07 16:12:51 +1200 |
| commit | 5d61bb6546d4c4045f302c0c2daf7594820e6507 (patch) | |
| tree | f204587af26451ee437ca8655e8a383a4d463834 /README.markdown | |
| parent | Remove fixed issue of `kill` completion (diff) | |
| download | dotfiles-5d61bb6546d4c4045f302c0c2daf7594820e6507.tar.gz dotfiles-5d61bb6546d4c4045f302c0c2daf7594820e6507.zip | |
Restore old code for describing Git prompt commit
I'm really confused. I could have sworn this was working correctly (i.e.
the --always option spat out a short reference to the commit as a
fallback), but I must have been wrong. Maybe I hadn't installed the
appropriate file when I was testing it.
At first I thought this was a bug introduced in Git 2.10, but the
short-circuit disregarding --always if --exact-match or --candidates=0
is set seems to have been in the `describe` builtin for ages. I must
have just tested poorly; I can't see any other explanation in the
source.
No matter; this isn't much slower.
Diffstat (limited to 'README.markdown')
0 files changed, 0 insertions, 0 deletions