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

Re: What will come after Git 2.56?

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Sep 8, 2026, 15:59 UTC
Message-ID
<aqAw3a3Ek0EZg0CH@fruit.crustytoothpaste.net>
In-Reply-To
<010801dd3fa9$3277ae30$97670a90$@nexbridge.com>
On 2026-09-08 at 15:46:16, rsbecker@nexbridge.com wrote:
Show 8 quoted lines
> On September 6, 2026 2:15 PM, brian m. carlson wrote:
> >Similarly, I am not aware of anyone who is seriously undertaking Rust support for
> >platforms that do not already support it, so I don't think that should be a blocker,
> >either.
> 
> Actually, I may have some news on that score. While it is unlikely to make 3.0, it
> could be soon after. Unfortunately, all info is NDA, so I cannot really publicise it
> at this point. I remain very hopeful.

I'm very pleased to hear that some progress might be being made. I, too, am hopeful that NonStop or other platforms might provide a suitable Rust port that would work with Git.

-- 
brian m. carlson (they/them)
Toronto, Ontario, CA
Previous: rsbecker@nexbridge.com
Message 13 of 13 in “What will come after Git 2.56?”
  1. Junio C HamanoSep 6, 2026
  2. brian m. carlsonSep 6, 2026
  3. Patrick SteinhardtSep 7, 2026
  4. Harald NordgrenSep 24, 2026
  5. Junio C HamanoSep 24, 2026
  6. Changing default config values (was Re: What will come after Git 2.56?)Phillip Wood, Sep 27, 2026
  7. Junio C HamanoSep 27, 2026
  8. Jeff KingSep 28, 2026
  9. Kristoffer HaugsbakkSep 25, 2026
  10. D. Ben KnobleSep 25, 2026
  11. Emily ShafferSep 7, 2026
  12. rsbecker@nexbridge.comSep 8, 2026
  13. brian m. carlsonSep 8, 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.