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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Am 14.05.2009, 02:53 Uhr, schrieb Matthias Andree <matthias.andree@xxxxxx>:


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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]