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

Re: [PATCH v2 0/4] Enable Rust by default

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Apr 10, 2026, 21:48 UTC
Message-ID
<adlwGv8LPdfwP8Yv@fruit.crustytoothpaste.net>
In-Reply-To
<xmqq4ilio6wp.fsf@gitster.g>
On 2026-04-10 at 21:13:42, Junio C Hamano wrote:
Show 13 quoted lines
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 
> > This was actually sent out just before rc0, but Patrick requested some
> > changes in v1.  (I forgot to thread it to the previous version,
> > unfortunately.)
> 
> Proudly saying "It was sent before rc0", as if that gave community
> plenty of time to adjust, is not something I was expecting to hear.
> 
> "This is expected to be a big impact change, so I am sending it
> before -rc0 of this cycle, so that it can be in the first batch that
> graduates to 'master' for the next cycle" would have been a lot more
> understandable, though.

This change was announced on the list and in the documentation, so its appearance should not be a surprise.

I didn't realize that I was sending it directly before -rc0 because I'm not usually very attuned to the timeframe in between releases, to be honest. I usually send patches as my schedule allows and I try to fix anything I've broken relatively quickly and even faster in the -rc period, and I generally let you decide how and when to merge them.

In this particular case, I merely remembered that it was something we committed to because I actually was looking at the BreakingChanges document for other reasons, so I sent a patch as soon as possible. That just happened to be right before -rc0. Had I remembered earlier, I would of course have sent the patch earlier. It appears, however, that we all had a memory lapse in this case and I do apologize for my part in that.

I don't have a strong opinion here and if you prefer, we can defer to 2.55. I agree that would be less risky at this point in the release cycle and, of course, you are the maintainer.

I have been operating under the assumption that Git 3.0 is destined for September 2026 based on the discussions we had at the September 2024 Contributors' Summit in Berlin where we said 1–2 years, as well as other discussions on the list, and that is the message I have been communicating to other people and projects[0]. I am fully aware that that date might slip due to various reasons[1], but I do very much want to get as many things set up as possible so people can test and there will be fewer surprises, which was of course the reason for sending in this series. I imagine, for instance, that Debian might ship a WITH_BREAKING_CHANGES version in experimental for testing to find all the exciting things that will break (of which I am aware of quite a few). (I will suggest that to them shortly.)

[0] This is true in both my personal and professional roles. [1] Although I am unable to be more specific, let us just say that I am endeavouring to do everything I can such that the date does not slip for any reasons within my control.

-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: Junio C HamanoNext: Derrick Stolee
Message 13 of 14 in “Enable Rust by default”
  1. 0/4 Enable Rust by defaultbrian m. carlson, Apr 9, 2026
  2. 1/4 docs: update version with default Rust supportbrian m. carlson, Apr 9, 2026
  3. 3/4 Linux: link against libdlbrian m. carlson, Apr 9, 2026
  4. 4/4 Enable Rust by defaultbrian m. carlson, Apr 9, 2026
  5. 2/4 ci: install cargo on Alpinebrian m. carlson, Apr 9, 2026
  6. Derrick StoleeApr 10, 2026
  7. Re*: [PATCH v2 0/4] Enable Rust by defaultJunio C Hamano, Apr 10, 2026
  8. Derrick StoleeApr 10, 2026
  9. brian m. carlsonApr 10, 2026
  10. Junio C HamanoApr 10, 2026
  11. brian m. carlsonApr 10, 2026
  12. Junio C HamanoApr 10, 2026
  13. brian m. carlsonApr 10, 2026
  14. Derrick StoleeApr 10, 2026

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.