"Shawn O. Pearce" <spearce@xxxxxxxxxxx> writes: > If the user has been using reflog for a long time (e.g. since its > introduction) then it is very likely that an existing branch's > reflog may still mention commits which have long since been pruned > out of the repository. I've thought about this issue when I did the repack/prune; my take on this was you should prune reflog first then repack. - 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