From: Junio C Hamano <gitster@pobox.com>
To: Marek Vasut <marex@denx.de>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [BUG] git clone -q ends with early EOF
Date: Wed, 18 Sep 2013 09:03:30 -0700 [thread overview]
Message-ID: <xmqqzjraunfx.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <201309181444.19070.marex@denx.de> (Marek Vasut's message of "Wed, 18 Sep 2013 14:44:18 +0200")
This sounds suspiciously like 05e95155 (upload-pack: send keepalive
packets during pack computation, 2013-09-08) that is cooking in
'next'.
If you are talking with other people's server side, you are SOL
until the server end gets the patch.
next prev parent reply other threads:[~2013-09-18 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 12:44 [BUG] git clone -q ends with early EOF Marek Vasut
2013-09-18 16:03 ` Junio C Hamano [this message]
2013-09-18 18:14 ` Jeff King
2013-09-18 19:50 ` Junio C Hamano
2013-09-18 20:55 ` Marek Vasut
2013-09-20 13:58 ` Marek Vasut
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=xmqqzjraunfx.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=marex@denx.de \
--cc=peff@peff.net \
/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.