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

[Suggestion] Handling Rust in upcoming releases

From
rsbecker@nexbridge.com <rsbecker@nexbridge.com>
Date
Aug 26, 2025, 18:04 UTC
Message-ID
<014e01dc16b3$dfae4750$9f0ad5f0$@nexbridge.com>
Hi All,

I would like to propose a mechanism where some platforms can keep using git even where Rust is not available.

Basically, make Rust a dependency for commands that need Rust but for those that are still in C, do not require rust. This will mean that git can keep being available, but new development can be done in Rust. It also means that CVE patches, if they come, can be done without leaving non-Rust platforms hanging out in the cold. It does mean that some commands will not be available on some platforms. This has been a well-established position by git for many years for other non-portable dependencies, like p4, subversion, and send-mail.

Please consider this as a compatibility suggestion. It will give platforms who have plans to implement Rust (eventually), time to react, as Rust is a non-trivial port without gcc being available also.

Sincerely, Randall

-- Brief whoami: NonStop&UNIX developer since approximately UNIX(421664400) NonStop(211288444200000000) -- In real life, I talk too much.

Next: brian m. carlson
Message 1 of 2 in “[Suggestion] Handling Rust in upcoming releases”
  1. rsbecker@nexbridge.comAug 26, 2025
  2. brian m. carlsonAug 27, 2025

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.