From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #11; Mon, 29)
Date: Tue, 30 Sep 2025 07:43:15 -0700 [thread overview]
Message-ID: <xmqqikh057cs.fsf@gitster.g> (raw)
In-Reply-To: <aNsQ5UjjbqJr8_Ik@fruit.crustytoothpaste.net> (brian m. carlson's message of "Mon, 29 Sep 2025 23:06:13 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> 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.
Thanks!
next prev parent reply other threads:[~2025-09-30 14:43 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
2025-09-30 14:43 ` Junio C Hamano [this message]
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=xmqqikh057cs.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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.