On 4/23/08, Jeff King <peff@xxxxxxxx> wrote: > + > +Notes > +----- > + > +git-gc tries very hard to be safe about the garbage it collects. In > +particular, it will keep not only objects referenced by your current set > +of branches and tags, but also objects referenced by the index, remote > +tracking branches, refs saved by linkgit:git-filter-branch[1] in > +refs/original/, or reflogs (which may references commits in branches > +that were later amended or rewound). > + > +If you are expecting some objects to be collected and it isn't, check > +all of those locations and decide whether it makes sense in your case to > +remove those references. > + This information would have helped me quite a bit when I first encountered this problem. It would be nice if it also showed up under git-prune (since git-gc doesn't delete anything itself, if I understand correctly). Also a link to some information about reflogs (even just to "see also" git-reflog) would help, since I didn't hear about reflogs at all until after I joined the mailing list. Avery -- 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
