Re: [PATCH] index-pack: speed up promisor link recording

From: Arijit Banerjee <arijit@effectiveailabs.com>
Date: Aug 2, 2026, 23:19 UTC
Message-ID: <CAFwoC-6eJNX4H7AeOcTdSbFRqkoqAOb2Js9Qj+93kHJWG7OkUQ@mail.gmail.com>
In-Reply-To: <xmqq7bm82l05.fsf@gitster.g>

Two suggestions:
- Maybe a karma system?
- A special release train that is more indulgent towards AI generated
code? Brave users can try out features and they get baked into stable
releases after enough soak time

Definitely not trying to be extractive, this one appears to be a decent size perf improvement!

Still holding on to a SHA1-DC hardware acceleration change, that one would admittedly be much harder to review ;)

On Sun, Aug 2, 2026 at 3:52 PM Junio C Hamano <gitster@pobox.com> wrote:

Show 19 quoted lines

>
> "brian m. carlson" <sandals@crustytoothpaste.net> writes:
>
> > I understand that the SubmittingPatches documentation is a bit long, but
> > I do suggest giving it at least a glance so you know what to expect.  I
> > think reading this sort of contributing documentation is more important
> > than ever since, in the era of LLMs, projects tend to have strong
> > opinions on what is and is not acceptable, not only just in terms of LLM
> > usage, but in how code and documentation are to be written and
> > formatted.
>
> Amen.
>
> Since we seem to be drawn into the AI policy discussion, are there
> things that we should consider borrowing from policies battle-tested
> by other projects?  I kind of like what LLVM has as "extractive
> contributions are rejected (whether it is AI or not AI)", as we are
> severely review-bandwidth limited these days.
>