On Tue, 10 Feb 2009, Shawn O. Pearce wrote: > Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > > > Is there some way to see if the pack it was writing is actually corrupt > > (beyond not having the hash set)? > > Hmm. If you have the pack fragment, its going to take some editing > to get it through the existing validation tools. Actually, I went for the other end; I made close_pack_windows() not mind the open windows (hey, it's dying anyway in my case, nobody's going to write more), and the results passed verification and "git fsck --full" with just a few dangling blobs and a dangling commit. So it seems to me that it has to be wrong information in memory. -Daniel *This .sig left intentionally blank* -- 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
