Jeff King <peff@xxxxxxxx> writes: > Subject: [PATCH] avoid 31-bit truncation in write_loose_object > > The size of the content we are adding may be larger than > 2.1G (i.e., "git add gigantic-file"). Most of the code-path > to do so uses size_t or unsigned long to record the size, > but write_loose_object uses a signed int. Thanks. I wonder if some analysis tool like sparse can help us spot these... -- 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
