From: <rsbecker@nexbridge•com>
To: <git@vger•kernel.org>
Subject: [Suggestion] Handling Rust in upcoming releases
Date: Tue, 26 Aug 2025 14:04:26 -0400 [thread overview]
Message-ID: <014e01dc16b3$dfae4750$9f0ad5f0$@nexbridge.com> (raw)
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 reply other threads:[~2025-08-26 18:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 18:04 rsbecker [this message]
2025-08-27 0:51 ` [Suggestion] Handling Rust in upcoming releases brian m. carlson
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='014e01dc16b3$dfae4750$9f0ad5f0$@nexbridge.com' \
--to=rsbecker@nexbridge$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox