Re: git-push: forced update of tag shows unabbreviated SHA1

Jeff King [off-list ref] writes:

On Thu, Jan 31, 2008 at 05:06:25AM -0500, Jeff King wrote:

quoted

But getting back to your point: yes, I agree it is a little ugly.
Rewriting find_unique_abbrev would be necessary for fixing it, and I'm
not sure it is worth the trouble.

Actually, it looks like we already handle a similar case: the null sha1,
so the change isn't that big (and the null sha1 case folds nicely into
the "missing" case).

Heh, "Make sure to abbreviate something that does not match" ---
I forgot about that trick I did looooooooong time ago ;-).

I like the idea.  Does it not break anything?