The patch returned by http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=462fb2af9788a82a534f8184abfde31574e1cfa0 is truncated. The page which refers to that patch, at http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=462fb2af9788a82a534f8184abfde31574e1cfa0, shows the full patch.
I am not subscribed to this list so please CC me in discussion.
Jeff KingRe: Truncated patch
On Fri, May 16, 2014 at 06:04:57PM +0930, David Newall wrote:
> The patch returned by http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=462fb2af9788a82a534f8184abfde31574e1cfa0 > is truncated. The page which refers to that patch, at http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=462fb2af9788a82a534f8184abfde31574e1cfa0, > shows the full patch.
Weird. It is truncated if I fetch it with "curl", but it looks fine in my browser. It's truncated at exactly 4K, and the transfer-encoding is chunked. Maybe cgit (or kernel.org's webserver) is doing something non-standard with chunking that the browser understands but curl does not?
-Peff
Jeff KingRe: Truncated patch
On Fri, May 16, 2014 at 04:51:16AM -0400, Jeff King wrote:
> On Fri, May 16, 2014 at 06:04:57PM +0930, David Newall wrote: > > > The patch returned by http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=462fb2af9788a82a534f8184abfde31574e1cfa0 > > is truncated. The page which refers to that patch, at http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=462fb2af9788a82a534f8184abfde31574e1cfa0, > > shows the full patch. > > Weird. It is truncated if I fetch it with "curl", but it looks fine in > my browser. It's truncated at exactly 4K, and the transfer-encoding is > chunked. Maybe cgit (or kernel.org's webserver) is doing something > non-standard with chunking that the browser understands but curl does > not?
I take it back. Now it is screwed up in my browser, too. Perhaps related to hitting different kernel.org servers (though all three IPs now give me the truncated output).
Looking at the raw protocol, the chunked encoding is fine; it literally just quits after 4K, and sends the 0-byte "all done" chunk. So I'm guessing it's either a bug in cgit, or a temporary error that erroneously ended up cached (I don't know enough about cgit's or kernel.org's caching infrastructure to say more).
-Peff