From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>, Patrick Steinhardt <ps@pks.im>,
Ezekiel Newren <ezekielnewren@gmail.com>
Subject: Re: [PATCH 0/4] Enable Rust by default
Date: Thu, 02 Apr 2026 22:04:49 -0700 [thread overview]
Message-ID: <xmqqldf4ocr2.fsf@gitster.g> (raw)
In-Reply-To: <20260403011249.4133372-1-sandals@crustytoothpaste.net> (brian m. carlson's message of "Fri, 3 Apr 2026 01:12:45 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> Our breaking changes document said that we would enable Rust support by
> default in Git 2.53, while still leaving the ability for it to be
> disabled. Unfortunately, we forgot to do that and my time machine is
> broken right now, so this series sets it up for Git 2.54.
>
> The first patch updates the documentation accordingly and the next two
> fix a few cases that are broken in our CI system. The final patch
> simply enables Rust by default except for two jobs to make sure that we
> continue to build correctly without Rust for the moment.
>
> I didn't force Rust on with the breaking changes mode because it's
> already on by default with this series and it seemed unnecessary.
Thanks.
>
> The GitHub Actions CI passes on all platforms with this series.
>
> brian m. carlson (4):
> docs: update version with default Rust support
> ci: install cargo on Alpine
> Linux: link against libdl
> Enable Rust by default
>
> Documentation/BreakingChanges.adoc | 2 +-
> Makefile | 10 +++++-----
> ci/install-dependencies.sh | 2 +-
> ci/lib.sh | 3 +++
> ci/run-build-and-tests.sh | 2 +-
> config.mak.uname | 1 +
> meson.build | 2 +-
> meson_options.txt | 2 +-
> 8 files changed, 14 insertions(+), 10 deletions(-)
prev parent reply other threads:[~2026-04-03 5:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 1:12 [PATCH 0/4] Enable Rust by default brian m. carlson
2026-04-03 1:12 ` [PATCH 1/4] docs: update version with default Rust support brian m. carlson
2026-04-03 1:12 ` [PATCH 2/4] ci: install cargo on Alpine brian m. carlson
2026-04-08 10:12 ` Patrick Steinhardt
2026-04-03 1:12 ` [PATCH 3/4] Linux: link against libdl brian m. carlson
2026-04-08 10:12 ` Patrick Steinhardt
2026-04-03 1:12 ` [PATCH 4/4] Enable Rust by default brian m. carlson
2026-04-08 10:12 ` Patrick Steinhardt
2026-04-03 5:04 ` 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=xmqqldf4ocr2.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ezekielnewren@gmail.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=sandals@crustytoothpaste.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.