From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, "Elijah Newren" <newren@gmail.com>,
"Jeff King" <peff@peff.net>,
"Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: Re: proto v2 fixes for maint (was Re: Preparing for a Git 2.26.3 release)
Date: Tue, 28 Apr 2020 11:19:55 -0700 [thread overview]
Message-ID: <xmqqd07r322c.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <xmqq7dxz4j62.fsf@gitster.c.googlers.com> (Junio C. Hamano's message of "Tue, 28 Apr 2020 10:25:09 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> In short, my preference is to ship 2.26.3 with the "demote v2 from
> default", and hopefully try 2.27 with "v2 with negotiation fix" and
> hope people won't find any other remaining glitches in 2.27. After
> that, we may want to merge the negotiation fix down to 2.26.x track
> but I am not comfortable merging it in a release on the maintenance
> track with the timeframe we seem to be talking about (i.e. a few
> weeks, presumably).
The last part needs clarification. What I am hesitant is to merge
only the "negotiation fix" in 2.26.3 while keeping v2 the default.
As long as v2 is not the default with the "demote" patch, I am OK
to have the "negotiation fix" in there, too.
next prev parent reply other threads:[~2020-04-28 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 5:55 Preparing for a Git 2.26.3 release Jonathan Nieder
2020-04-28 6:22 ` Elijah Newren
2020-04-28 17:25 ` proto v2 fixes for maint (was Re: Preparing for a Git 2.26.3 release) Junio C Hamano
2020-04-28 18:16 ` Michal Suchánek
2020-04-28 18:19 ` Junio C Hamano [this message]
2020-04-29 5:56 ` Jonathan Nieder
2020-05-08 22:26 ` Preparing for a Git 2.26.3 release Junio C Hamano
2020-05-09 7:07 ` Johannes Schindelin
2020-05-09 17:11 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd07r322c.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=newren@gmail.com \
--cc=peff@peff.net \
/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.