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

On Thu, Jan 31, 2008 at 02:38:37AM -0800, Junio C Hamano wrote:

quoted

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?

No idea. :) I will hold onto it and submit a cleaned up version
post-1.5.4.

-Peff