From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2013, #08; Tue, 19)
Date: Wed, 20 Feb 2013 03:50:40 -0500 [thread overview]
Message-ID: <20130220085040.GA31996@sigill.intra.peff.net> (raw)
In-Reply-To: <7v621nzaxb.fsf@alter.siamese.dyndns.org>
On Tue, Feb 19, 2013 at 11:44:48PM -0800, Junio C Hamano wrote:
> * jk/smart-http-robustify (2013-02-17) 3 commits
> - remote-curl: sanity check ref advertisement from server
> - remote-curl: verify smart-http metadata lines
> - pkt-line: teach packet_get_line a no-op mode
>
> Parse the HTTP exchange that implements the native Git protocol as
> a series of stateless RPC more carefully to diagnose protocol
> breakage better.
>
> Will merge to and hold in 'next'.
I just posted elsewhere, but to make sure I get your attention: please
hold off on this. The sanity check in the top patch is not right
(because of the ERR/flush thing that Jonathan brought up). I'll have an
updated series tomorrow.
-Peff
prev parent reply other threads:[~2013-02-20 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 7:44 What's cooking in git.git (Feb 2013, #08; Tue, 19) Junio C Hamano
2013-02-20 8:50 ` 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=20130220085040.GA31996@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).