git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Jeff King <peff@peff.net>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	Junio C Hamano <gitster@pobox.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Jonathan Tan <jonathantanmy@google.com>,
	git@vger.kernel.org
Subject: Re: Fetching 24 Linux commits = 1.2 GiB
Date: Mon, 25 May 2020 20:22:05 +0200	[thread overview]
Message-ID: <20200525182205.7hcffndaro2pgink@wunner.de> (raw)
In-Reply-To: <20200520194019.GA340985@coredump.intra.peff.net>

On Wed, May 20, 2020 at 03:40:19PM -0400, Jeff King wrote:
> The "too big fetch" issue has since been fixed in "master", as well as
> reverting the switch to the v2 protocol (which I think is just
> belt-and-suspenders; AFAIK there are no known issues after the fix).
> Both will be in v2.27. I don't see anything on "maint", but they _could_
> be part of an eventual v2.26.3.
> 
> The fix was merged in 0b07eecf6e (Merge branch 'jt/v2-fetch-nego-fix',
> 2020-05-01) for reference.

Please consider cutting a v2.26.3 release with this fix at your
earliest convenience.  The waste of bandwidth is mind-boggling.
(> 1 GByte whenever fetching from a kernel remote.)

Thanks,

Lukas

  reply	other threads:[~2020-05-25 18:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15  8:01 Fetching 24 Linux commits = 1.2 GiB Jiri Slaby
2020-04-15  8:11 ` Andreas Schwab
2020-04-15  8:16   ` Jiri Slaby
2020-04-15  8:23     ` Andreas Schwab
2020-04-15  8:27       ` Jiri Slaby
2020-04-15  8:34         ` Andreas Schwab
2020-04-15 10:52 ` Kevin Daudt
2020-04-15 13:56 ` Konstantin Ryabitsev
2020-04-15 15:08   ` Junio C Hamano
2020-04-15 15:16     ` Jeff King
2020-04-15 18:52     ` Jonathan Nieder
2020-05-20  8:53     ` Andreas Schwab
2020-05-20  8:57       ` Andreas Schwab
2020-05-20 10:05       ` Michal Suchánek
2020-05-20 10:34         ` Andreas Schwab
2020-05-20 19:40       ` Jeff King
2020-05-25 18:22         ` Lukas Wunner [this message]
2020-05-25 18:37           ` Junio C Hamano
2020-04-16  6:31   ` Jiri Slaby
2020-04-21 10:02     ` Martin Wilck

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200525182205.7hcffndaro2pgink@wunner.de \
    --to=lukas@wunner.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jonathantanmy@google.com \
    --cc=jrnieder@gmail.com \
    --cc=peff@peff.net \
    --cc=schwab@linux-m68k.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).