From: Junio C Hamano <gitster@pobox.com>
To: Ben Knoble <ben.knoble@gmail.com>
Cc: Kurt Mielke <scr@lyn.dk>, git@vger.kernel.org
Subject: Re* CARGO trouble appeared from 2.54.0 to 2.55.0
Date: Mon, 06 Jul 2026 07:13:13 -0700 [thread overview]
Message-ID: <xmqq8q7ocikm.fsf_-_@gitster.g> (raw)
In-Reply-To: <81CE676D-CBBD-44E9-8DD6-B34068E35769@gmail.com> (Ben Knoble's message of "Sun, 5 Jul 2026 19:56:23 -0400")
Ben Knoble <ben.knoble@gmail.com> writes:
> Git’s source code has included some optional Rust components for
> a few releases now. Rust is planned to be a requirement for 3.0
> (IIUC), but I don’t have any recollection of the proposed
> timeline. [There was also some discussion of delaying the Rust
> mandate timeline for platforms which currently lack support?]
> ...
> 2.55 is the first version to flip the default to « build with Rust
> », but it remains optional as you’ve discovered.
> ...
> Searching the internet shows Alma has packages for Rust, which you
> should be able to install if you want to compile with the Rust
> components.
As you said above, what was reported is totally expected (I
understand that 2.55 built properly for the OP with "make
NO_RUST=NoThanks" set).
I do not know why nobody complained, but we have been carrying this
incomplete sentence in the release notes forever X-<.
Documentation/RelNotes/2.55.0.adoc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git c/Documentation/RelNotes/2.55.0.adoc w/Documentation/RelNotes/2.55.0.adoc
index f5643534dc..696ad15c1e 100644
--- c/Documentation/RelNotes/2.55.0.adoc
+++ w/Documentation/RelNotes/2.55.0.adoc
@@ -85,8 +85,8 @@ Performance, Internal Implementation, Development Support etc.
* Promisor remote handling has been refactored and fixed in
preparation for auto-configuration of advertised remotes.
- * Rust support is enabled by default (but still allows opting out) in
- some future version of Git.
+ * Rust support is enabled by default (but still allows opting out); in
+ some future version of Git, this will become mandatory.
* Preparation of the xdiff/ codebase to work with Rust.
prev parent reply other threads:[~2026-07-06 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 0:21 CARGO trouble appeared from 2.54.0 to 2.55.0 Kurt Mielke
2026-07-05 23:56 ` Ben Knoble
2026-07-06 14:13 ` Junio C Hamano [this message]
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=xmqq8q7ocikm.fsf_-_@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=scr@lyn.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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