From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-Status: No, score=-3.5 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_PASS, SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by dcvr.yhbt.net (Postfix) with ESMTP id 844501F55B for ; Wed, 20 May 2020 10:05:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726791AbgETKFc (ORCPT ); Wed, 20 May 2020 06:05:32 -0400 Received: from mx2.suse.de ([195.135.220.15]:57356 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726403AbgETKFb (ORCPT ); Wed, 20 May 2020 06:05:31 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 1AC26AC40; Wed, 20 May 2020 10:05:33 +0000 (UTC) Date: Wed, 20 May 2020 12:05:28 +0200 From: Michal =?iso-8859-1?Q?Such=E1nek?= To: Andreas Schwab Cc: Junio C Hamano , Jonathan Nieder , Jonathan Tan , git@vger.kernel.org Subject: Re: Fetching 24 Linux commits = 1.2 GiB Message-ID: <20200520100528.GV25173@kitsune.suse.cz> References: <20200415135627.vx75hsphbpmgrquv@chatter.i7.local> <87sgfvq967.fsf@igel.home> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87sgfvq967.fsf@igel.home> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Wed, May 20, 2020 at 10:53:36AM +0200, Andreas Schwab wrote: > On Apr 15 2020, Junio C Hamano wrote: > > > Do these (and I think we saw other reports) make us rethink the > > status of protocol v2 as the default? Are all of these fallouts > > we saw so far easy-to-fix bugs, or are there more fundamental issues > > in the v2 protocol design? > > I'm now seeing the issue myself, and can provide a backup of the > offending repository. What git version? Should be fixed in git 2.26.2 in SUSE and git 2.26.3 upstream. Thanks Michal