From: Jeff King <peff@peff.net>
To: David Newall <davidn@davidnewall.com>
Cc: git@vger.kernel.org
Subject: Re: Truncated patch
Date: Fri, 16 May 2014 05:24:58 -0400 [thread overview]
Message-ID: <20140516092458.GD21468@sigill.intra.peff.net> (raw)
In-Reply-To: <20140516085116.GC21468@sigill.intra.peff.net>
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
prev parent reply other threads:[~2014-05-16 9:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 8:34 Truncated patch David Newall
2014-05-16 8:51 ` Jeff King
2014-05-16 9:24 ` Jeff King [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140516092458.GD21468@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=davidn@davidnewall.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).