>
> Give an object a human readable name based on an available ref
>
> or something like that?
will use
> Or a sentence in BUGS section.
will add.
> A case (or two) I find more interesting is to see how the code
> behaves against these:
>
> git tag -a -m "annotated blob" a-blob HEAD:Makefile
> git tag -a -m "annotated tree" a-tree HEAD:t
> git describe a-blob a-tree
Glad I added a test for exactly this (well only the a-blob case,
but a-tree will be the same):
test_expect_success 'describe tag object' '
git tag test-blob-1 -a -m msg unique-file:file &&
test_must_fail git describe test-blob-1 2>actual &&
grep "fatal: test-blob-1 is neither a commit nor blob" actual
'
