From: Jeff King <peff@peff.net>
To: "Keller, Jacob E" <jacob.e.keller@intel.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"wipedout@yandex.ru" <wipedout@yandex.ru>
Subject: Re: [PATCH] remote-curl: do not complain on EOF from parent git
Date: Wed, 9 Jul 2014 17:42:17 -0400 [thread overview]
Message-ID: <20140709214217.GD25854@sigill.intra.peff.net> (raw)
In-Reply-To: <1404941118.23510.34.camel@jekeller-desk1.amr.corp.intel.com>
On Wed, Jul 09, 2014 at 09:25:18PM +0000, Keller, Jacob E wrote:
> On Wed, 2014-07-09 at 17:20 -0400, Jeff King wrote:
> > The parent git process is supposed to send us an empty line
> > to indicate that the conversation is over. However, the
> > parent process may die() if there is a problem with the
> > operaiton (e.g., we try to fetch a ref that does not exist).
>
> Nitpick, but you probably meant operation here.
I did (and I probably meant to turn on spellcheck, too...).
I'll repost in a minute, as I have some follow-on patches. Thanks.
-Peff
next prev parent reply other threads:[~2014-07-09 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 7:37 "Unexpected end of command stream" message looks irrelevant when I try to pull a non-existing branch Dmitry
2014-07-09 20:59 ` Jeff King
2014-07-09 21:20 ` [PATCH] remote-curl: do not complain on EOF from parent git Jeff King
2014-07-09 21:25 ` Keller, Jacob E
2014-07-09 21:42 ` Jeff King [this message]
2014-07-09 21:45 ` [PATCH 1/3] " Jeff King
2014-07-09 21:47 ` [PATCH 2/3] remote-curl: use error instead of fprintf(stderr) Jeff King
2014-07-09 21:47 ` [PATCH 3/3] remote-curl: mark helper-protocol errors more clearly Jeff King
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=20140709214217.GD25854@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=jacob.e.keller@intel.com \
--cc=wipedout@yandex.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.