I'm a fairly cautious git user, and as such I frequently use lightweight tags to temporarily save a branch tip for every microscopic risk I stand of otherwise losing it. I also frequently use git gc to repack objects. However, just now I made a doodoo and need to recover a lost branch-head, so git lost-found to the rescue. Or so I thought... It turns out that since I've packed the unreachable refs, they haven't been pruned, and I can't for the life of me figure out how to get rid of them. I wrote a small script to create lightweight tags on all the SHA1's reported by lost-found and then used qgit to browse them and thus locate my lost branch tip, so the immediate problem is solved, , but the question remains: How do I get rid of packed commits that are no longer reachable? I know they don't affect disk usage all that much, and they most certainly don't affect daily development, but this once when I really needed to use git-lost-found, it was nearly useless because it reported some 600 unreachable revisions :-/ In a last-ditch desperate effort, I tried with git-unpack-objects as well, but it seems broken as it fails to create the loose objects under .git/objects/[0-f0-f]/. I'll look into that tonight if I get some spare time. -- Andreas Ericsson andreas.ericsson@xxxxxx OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 - 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
