From: Shawn Pearce Date: Fri, 22 Dec 2006 00:56:06 GMT Subject: Re: [PATCH 3/3] Don't crash during repack of a reflog with pruned commits. Message-ID: <20061222005606.GA14773@spearce.org> In-Reply-To: <20061222004906.GC14789@spearce.org> "Shawn O. Pearce" wrote: > 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. > > Rather than aborting with a very useless error message during > git-repack, pack as many valid commits as we can get from the > reflog and let the user know that the branch's reflog contains > already pruned commits. A future 'git reflog expire' (or whatever > it finally winds up being called) can then be performed to expunge > those reflog entries. If its not obvious from the patch, this doesn't entirely fix the problem. Just because the commit has not been pruned does not mean that a blob or tree referenced by that commit has not been pruned. Right now I am missing 1 blob and cannot repack because of it. At least with this series of 3 patches the error message resulting from this one missing blob is clearer. -- Shawn.