From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: Junio C Hamano <gitster@pobox•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #11; Mon, 29)
Date: Mon, 29 Sep 2025 23:06:13 +0000 [thread overview]
Message-ID: <aNsQ5UjjbqJr8_Ik@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqv7l06gwi.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On 2025-09-29 at 22:19:25, Junio C Hamano wrote:
> * ps/rust-balloon (2025-09-24) 9 commits
> - ci: enable Rust for breaking-changes jobs
> - ci: convert "pedantic" job into full build with breaking changes
> - BreakingChanges: announce Rust becoming mandatory
> - varint: reimplement as test balloon for Rust
> - varint: use explicit width for integers
> - help: report on whether or not Rust is enabled
> - Makefile: introduce infrastructure to build internal Rust library
> - Makefile: reorder sources after includes
> - meson: add infrastructure to build internal Rust library
>
> Dip our toes a bit to (optionally) use Rust implemented helper
> called from our C code.
>
> Comments?
This looks fine to me and addressed all of my previous feedback. The
cover letter incorrectly says that it's only wiring up Meson (which is
no longer true), but we're not including that in the series, so we don't
need to fix it.
I confirmed that my branch using Rust builds fine on top of that version
as well.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2025-09-29 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-29 22:19 What's cooking in git.git (Sep 2025, #11; Mon, 29) Junio C Hamano
2025-09-29 23:06 ` brian m. carlson [this message]
2025-09-30 14:43 ` Junio C Hamano
2025-09-30 19:58 ` Ezekiel Newren
2025-10-02 10:02 ` Karthik Nayak
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=aNsQ5UjjbqJr8_Ik@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/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