Re: git-tag bug? confusing git fast-export with double tag objects

From: Alex Riesen <raa.lkml@gmail.com>
Date: May 14, 2009, 13:16 UTC
Message-ID: <81b0412b0905140616h69ac2919j26734f02455a5f5c@mail.gmail.com>
In-Reply-To: <op.utw7buoi1e62zd@balu>

2009/5/14 Matthias Andree <matthias.andree@gmx.de>:

Show 8 quoted lines

> Am 14.05.2009, 14:16 Uhr, schrieb Alex Riesen <raa.lkml@gmail.com>:
>>
>> As soon as an object is not referenced anymore by any reference (including
>> references from refs/tags/), reference log or index it will be removed by
>> garbage collection (gc, prune) at the next opportunity.
>
> Irrelevant, because your assumption "not referenced anymore" is false. This
> was clearly written in my earlier message, which please see.

Yes, in your case it stays referenced, through the new tag which the reference refs/tags/foo _now_ points to. Tough luck. In this particular case you could just remove the reference (that's refs/tags/foo now), repack and re-tag (properly).

It may be not what your wanted, but it is how it is expected to work. If git tag would reduce its arguments down to commits, it would be impossible to sign tags at all (strictly speaking: it would be impossible to create a tag, referencing another tag). Which is useful thing to have.