From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>,
git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.27.0-rc1
Date: Wed, 20 May 2020 15:31:56 -0400 [thread overview]
Message-ID: <20200520193156.GA4700@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqsgfuv2ko.fsf@gitster.c.googlers.com>
On Wed, May 20, 2020 at 12:17:11PM -0700, Junio C Hamano wrote:
> Git 2.27 Release Notes (draft)
> ==============================
>
> Updates since v2.26
> -------------------
>
> Backward compatibility notes
Is it worth mentioning here the reversion of v2 as the default protocol?
It does end up (along with the actual code fix) in the "fixes from
v2.26" section:
> * Those fetching over protocol v2 from linux-next and other kernel
> repositories are reporting that v2 often fetches way too much than
> needed.
> (merge 11c7f2a30b jn/demote-proto2-from-default later to maint).
>
> * The upload-pack protocol v2 gave up too early before finding a
> common ancestor, resulting in a wasteful fetch from a fork of a
> project. This has been corrected to match the behaviour of v0
> protocol.
> (merge 2f0a093dd6 jt/v2-fetch-nego-fix later to maint).
but that's somewhat buried. I dunno. It is not likely to introduce _new_
compatibility issues, but perhaps folks looking into compatibility stuff
may want to know about the revert.
-Peff
next prev parent reply other threads:[~2020-05-20 19:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 19:17 [ANNOUNCE] Git v2.27.0-rc1 Junio C Hamano
2020-05-20 19:31 ` Jeff King [this message]
2020-05-20 20:02 ` Junio C Hamano
2020-05-20 20:31 ` Re* " Junio C Hamano
2020-05-20 21:24 ` Jeff King
2020-05-20 22:00 ` Protocol v2 in v2.27 (Re: Re* [ANNOUNCE] Git v2.27.0-rc1) Jonathan Nieder
2020-05-20 23:59 ` Junio C Hamano
2020-05-21 0:29 ` Jeff King
2020-05-21 2:15 ` Jonathan Nieder
2020-05-21 2:35 ` Carlo Marcelo Arenas Belón
2020-05-21 2:45 ` connect: don't request v2 when pushing (Re: Protocol v2 in v2.27) Jonathan Nieder
2020-05-21 3:26 ` Carlo Marcelo Arenas Belón
2020-05-21 11:54 ` Protocol v2 in v2.27 (Re: Re* [ANNOUNCE] Git v2.27.0-rc1) Derrick Stolee
2020-05-21 16:42 ` Junio C Hamano
2020-05-21 16:34 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2020-05-20 20:57 [ANNOUNCE] Git v2.27.0-rc1 Son Luong Ngoc
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=20200520193156.GA4700@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.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).