git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: proto v2 fixes for maint (was Re: Preparing for a Git 2.26.3 release)

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 28, 2020, 18:19 UTC
Message-ID
<xmqqd07r322c.fsf@gitster.c.googlers.com>
In-Reply-To
<xmqq7dxz4j62.fsf@gitster.c.googlers.com>
Junio C Hamano <gitster@pobox.com> writes:
Show 7 quoted lines
> 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.

Previous: Michal SuchánekNext: Jonathan Nieder
Message 5 of 9 in “Preparing for a Git 2.26.3 release”
  1. Jonathan NiederApr 28, 2020
  2. Elijah NewrenApr 28, 2020
  3. proto v2 fixes for maint (was Re: Preparing for a Git 2.26.3 release)Junio C Hamano, Apr 28, 2020
  4. Michal SuchánekApr 28, 2020
  5. Junio C HamanoApr 28, 2020
  6. Jonathan NiederApr 29, 2020
  7. Junio C HamanoMay 8, 2020
  8. Johannes SchindelinMay 9, 2020
  9. Junio C HamanoMay 9, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.