Re: git-tag bug? confusing git fast-export with double tag objects
- From
- Matthias Andree <matthias.andree@gmx.de>
- Date
- May 14, 2009, 02:13 UTC
- Message-ID
- <op.utwdsutn1e62zd@merlin.emma.line.org>
- In-Reply-To
- <op.utv93sdo1e62zd@merlin.emma.line.org>
Am 14.05.2009, 02:53 Uhr, schrieb Matthias Andree <matthias.andree@gmx.de>:
> 2. how do I trash the accidentally created 2nd "baz" tag object, i. e. > remove it from the (packed) object database? Of course, I can hack some > script (or use a text editor) to grind this git-fast-export into shape > and re-importing it...
OK, that worked: I traced (with git cat-file) the tree through all tagged tag until the first tagged commit, and hack packed-refs (or refs/tags/foo) to point to the commit object, and afterwards prune the dangling tag.
However, the other questions remain. I'd think git tag should dereference its 2nd non-option argument to a commit before laying down the tag...
-- Matthias Andree