Eric Wong <normalperson@xxxxxxxx> wrote: > Eric Wong <normalperson@xxxxxxxx> wrote: > The verdict is still out on all patches and attempts I've posted > to fix the segfault. I'm quite busy at the moment and won't > be attending to git-svn things for another few days. Ok, those didn't work. I'm still preoccupied with another project that has a higher priority; and I've come down with a cold so if anybody else wants to step up to the plate, please take a stab at it. This issue has NOT been known to cause data corruption from any users that experienced it[1]. It seems to be happening in between when changesets are actually fetched. [1] - if there is any corruption to a particular file, it'll trigger an MD5 mismatch the next time that file is updated. -- Eric Wong - 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