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: Re* [ANNOUNCE] Git v2.27.0-rc1
Date: Wed, 20 May 2020 17:24:44 -0400 [thread overview]
Message-ID: <20200520212444.GA590699@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqq5zcquz4t.fsf_-_@gitster.c.googlers.com>
On Wed, May 20, 2020 at 01:31:30PM -0700, Junio C Hamano wrote:
> The promotion in Git 2.26 was buried in the "performance &
> implementation details" section and not in the backward
> compatibility section, so it feels a bit funny to highlight the
> reversion. In any case, here is what I prepared (but not committed
> yet)
Hmm, yeah, that does make it feel funny. I'd argue that it probably
would have been worth promoting a bit more in v2.26, but it is obviously
too late now.
> -- >8 --
> Subject: [PATCH] RelNotes: advertise the demotion of protocol v2
What you have here looks fine, but I'd be OK if we just left it as-is,
too, given the v2.26 mention.
-Peff
next prev parent reply other threads:[~2020-05-20 21:24 UTC|newest]
Thread overview: 15+ 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
2020-05-20 20:02 ` Junio C Hamano
2020-05-20 20:31 ` Re* " Junio C Hamano
2020-05-20 21:24 ` Jeff King [this message]
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
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=20200520212444.GA590699@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).