Re: [PATCH RFC v4 7/9] BreakingChanges: announce Rust becoming mandatory
On Wed, Sep 10, 2025 at 11:42:05PM +0200, Kristoffer Haugsbakk wrote:
Show 39 quoted lines
> On Wed, Sep 10, 2025, at 17:35, Patrick Steinhardt wrote:
> > +These changes are meant as test balloons to allow distributors of Git
> > to prepare
> > +for Rust becoming a mandatory part of the build process. There will be
> > multiple
> > +milestones for the introduction of Rust:
> > ++
> > +1. Initially, with Git 2.52, support for Rust will be auto-detected by
> > Meson and
> > + disabled in our Makefile so that the project can sort out the
> > initial
> > + infrastructure.
> > +2. In Git 2.53, both build systems will default-enable support for
> > Rust.
> > + Consequently, builds will break by default if Rust is not available
> > on the
> > + build host. The use of Rust can still be explicitly disabled via
> > build
> > + flags.
> > +3. In Git 3.0, the build options will be removed and support for Rust
> > is
> > + mandatory.
> > ++
>
> Some minutiae: the HTML output is like
>
> 3. In Git 3.0, ...
>
> You can explicitly ...
>
> But it seems from the text that the paragraph after (3) should go back
> to the previous level:
>
> 3. In ...
>
> You ...
>
> You’ll need to put these three list items in an `--` in order to get the
> latter. Or that’s one option (that I tried).
Ah, indeed. Thanks for your careful eyes, fixed locally now.
Patrick