Subject: Re: [PATCH v2 00/10] Use rust types in xdiff.

From: Junio C Hamano <[email-masked]>
Date: Thu, 18 Sep 2025 17:33:45 -0700

"Ezekiel Newren via GitGitGadget" <[email-masked]> writes:

> Changes since v1, to address review feedback.
>
>  * Only include the clean up patches; The remaining patches will be split
>    into a separate series.
>  * Commit message clarifications.
>  * Minor style cleanups.
>  * Performance impacts included in commit message of patch 8.
>
>
> Relevant part of the original cover letter follows:
> ===================================================
>
> This patch series involves ZERO Rust code and toolchains, which avoids the
> debate about Rust's portability and timeline. Instead, it shows how Git can
> immediately benefit from Rust's design choices without using it at all. The
> rationale for using Rust types on the C and Rust side is addressed in the
> commit that creates compat/rust_types.h.
>
> This patch series has 2 parts:
>
>  * Patches 1-9: Clean up xdiff, this can be merged without part 2.
>  * Patches 10-17: Define Rust types in compat/rust_types.h and then start
>    refactoring xdiff with Rust types. This depends on part 1.

This is probably stale.  If the patch numbering is to be trusted, we
are missing [09/10] (at least we haven't seen it in the list archive
30 minutes after the other messages in the series landed there), so
the "clean up xdiff" stage consists of 10 patches, and this cover
letter does not need to talk about "Patches 10-17" (yet).

Will see if lore.kernel.org catches up in the morning and process
them.  Thanks for working on the topic.