On Thu, Jan 17, 2008 at 12:58:07PM +0000, Johannes Schindelin wrote: > > Just a wild guess... Could it be that the mmap() happened before contents > were written to that fd? The faked mmap() is just a malloc() && pread(), > and would thus miss out on changes written after the mmap() call. This would be my guess too. As far as I can tell fast-import is creating objects directly in a packfile. I'm guessing here, but the new checking code is probably being triggered to check (for example) the parent ref for commits that fast-import is creating and the check only works if mmap can successfully examine objects in the still-being-written packfile. - 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
