|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|