Andreas Ericsson <ae@xxxxxx> writes: > 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. Sorry, I am a bit lost on what you are trying to achieve here. Are you trying to find the lost tip, or are you trying to remove objects that are only reachable from that lost tip? I thought lost-found was modified not to take reflogs into account specifically to support the former usage. > 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. Don't look into that -- unpack-objects won't explode objects that are already available in the repository. It is not "it fails" but "it was designed not to". - 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
