From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Dixit\, Ashutosh" <ashutosh.dixit@intel.com>,
git@vger.kernel.org, Jonathan Tan <jonathantanmy@google.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: Bug in 2.26: git-fetch fetching too many objects?
Date: Tue, 21 Apr 2020 12:16:51 -0700 [thread overview]
Message-ID: <xmqqblnkodi4.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <20200421064541.GG96152@google.com> (Jonathan Nieder's message of "Mon, 20 Apr 2020 23:45:41 -0700")
Jonathan Nieder <jrnieder@gmail.com> writes:
> (+cc: Jonathan Tan, fetch negotiation expert)
> Hi,
>
> Dixit, Ashutosh wrote:
>
>> I am seeing a strange behavior in git-fetch in 2.26. I frequently fetch
>> from a couple of linux kernel remotes (so you will have an idea how big the
>> repo is). I have a different system with 2.20 on which I never see a
>> problem.
> ...
> I suspect this is related to the change that protocol v2 does to use
> stateless-rpc even in stateful protocols. If my suspicion is correct,
> then the same behavior would show up with protocol v0 over http and
> https as well.
Thanks.
This is at least the fourth time we hear that v2 may not be ready
for the real-world use. Perhaps we should revert the default flip
on the maintenance track while we hunt for bugs and improve the
protocol support?
next prev parent reply other threads:[~2020-04-21 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 15:44 Bug in 2.26: git-fetch fetching too many objects? Dixit, Ashutosh
2020-04-20 17:03 ` Konstantin Ryabitsev
2020-04-21 5:18 ` Dixit, Ashutosh
2020-04-21 6:45 ` Jonathan Nieder
2020-04-21 19:16 ` Junio C Hamano [this message]
2020-04-21 19:36 ` Jonathan Nieder
2020-04-21 20:06 ` Junio C Hamano
2020-04-21 21:11 ` 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=xmqqblnkodi4.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=ashutosh.dixit@intel.com \
--cc=git@vger.kernel.org \
--cc=jonathantanmy@google.com \
--cc=jrnieder@gmail.com \
--cc=konstantin@linuxfoundation.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 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.