On Thu, May 27, 2010 at 3:57 PM, Chris Packham <judge.packham@xxxxxxxxx> wrote: > On Thu, May 27, 2010 at 3:18 PM, Chris Packham <judge.packham@xxxxxxxxx> wrote: >> On Thu, May 27, 2010 at 3:11 PM, Avery Pennarun <apenwarr@xxxxxxxxx> wrote: >>> On Thu, May 27, 2010 at 6:06 PM, Chris Packham <judge.packham@xxxxxxxxx> wrote: >>>> They're showing up with 'gitk --all'. I've made a backup so I can >>>> expire the reflog and see if they go away. >>> >>> gitk --all shouldn't be showing stuff just because it's in the reflog. >>> Does it have a branchname tag next to it? Have you exit/restarted >>> gitk or are you just using its refresh button? The latter doesn't >>> work very well across branch deletion. >>> >>> Avery >>> >> >> The commits do have tags. I'll try deleting them and gc'ing again. >> > > Deleting the tags seemed to do the trick as far as removing the > detached commits in gitk. > > Now git gc seems to be stuck > > ~/linux> git --version > git version 1.7.1 > > ~/linux> git gc > Counting objects: 20058 (went away made a coffee, came back still > stuck at 20058) > > I've attached with gdb and have the following trace if its of any use > (sorry I don't have debug symbols for libz). I've still got the > debugger attached if anyone wants me to dump out anything else. > Looks like its come back now. I guess there was just one object that was taking a while to pack. -- 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