On Thu, Jan 29, 2009 at 08:10:05AM -0500, David Abrahams wrote: > Good work. I don't know if this matters to you, but I think on a 32-bit > platform you'll find that size_t, which is supposed to be able to hold > the size of the largest representable *memory block*, is only 4 bytes > large: That should be fine; 32-bit systems can't deal with such large files anyway, since we want to address the whole thing. Getting around that would, as Andreas mentioned, involve dealing with large files in chunks, something that would make the code a lot more complex. So I think the answer is "tough, if you want files >4G get a 64-bit machine". Which is unreasonable for a file system to say, but I think is fine for git. -Peff -- 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
