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

--eqBhlv20JJinRjet
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[please avoid top-posting]

On 2026-08-02 at 22:54:27, Arijit Banerjee wrote:
> Maybe software can ship experimental versions which is more indulging
> towards AI generated patches? Brave users get to try the features and they
> can baked into stable releases once there's enough soak time.
>=20
> I have been holding onto my patch around hardware acceleration for SHA1-DC
> :)

The rationale, as Junio said, is based on the Developer's Certificate of
Origin.  That is a legal statement that a person has the legal right to
contribute those changes under the license and if they make a false or
misleading statement to that effect, they are responsible=E2=80=94legally a=
nd
otherwise=E2=80=94for it.

Considering the extensive litigation over LLM output at the moment, I
don't think anyone can clearly make that assertion.  Most of the
arguments I've heard are that it's fair use, which is a U.S. legal
concept.  That does not exist in Canada or the U.K., where there is fair
dealing, which is much more restricted.

If Company X includes LLM-generated code in their proprietary product
and it's found to be infringing in say, Germany, then they can simply
not distribute their code in Germany.  Git cannot do that: it's
distributed in Linux distributions around the planet, even in countries
subject to sanctions, such as Russia[0].  We must comply with the
license and the law everywhere in every country or we risk liability for
our contributors and distributors.  I, for one, am not willing to be
sued over this project and the project does not have the financial means
to deal with extensive litigation.

There are also concerns about the quality of the code and whether
submitters adequately understand the code well enough to have evaluated
and reviewed it thoroughly.  It's well known that when creating code
becomes cheap, the burden shifts to review and review becomes extremely
important.  That has been seen in lots of places, but we are an open
source project and we can't force contributors to do review like a
company can.  As Junio says, we already have trouble getting reviews
through and we don't want to make the problem worse.

LLM-generated content also has a negative quality reputation (see the
reaction to AI content in video games and books for an example) and
while all software has bugs, I appreciate the reputation that Git has
for quality and wish to retain that.

Those alone are reason enough for the policy, but there are other
concerns about the environmental impact, the impact on electricity and
hardware prices, the ethics of incorporating open source code without so
much as a credit[1], and a lot more.

So I don't think it's likely we're going to accept nontrivial
LLM-generated content in any capacity anytime soon and I don't think
trying to argue this or persuade us to accept it is going to be
productive or well received.  Of course, anyone can distribute their own
fork of Git with additional patches if they prefer, but we won't include
them.

[0] Debian, which distributes Git, has mirrors in Russia and Belarus:
https://www.debian.org/mirror/list
[1] For instance, as a member of ACM, I have to follow =C2=A7 1.5 (Respect
the work required to produce new ideas, inventions, creative works, and
computing artifacts) of the Code of Ethics:
https://www.acm.org/code-of-ethics.
--=20
brian m. carlson (they/them)
Toronto, Ontario, CA

--eqBhlv20JJinRjet
Content-Type: application/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

wr0EABYKAG8Fgmpv4VoJEHwMSWKIh6KBRxQAAAAAAB4AIHNhbHRAbm90YXRpb25z
LnNlcXVvaWEtcGdwLm9yZ1/7wDmaGuYSFcfBMc50yEuNphv/oNGBauD3mBKhcw+e
FiEECCzmip28ZfuD0cORfAxJYoiHooEAAJBkAP9LwfBWlzaSdmv1k1vKoo98RX0J
OHRodUyRPB24Uz5vgwD/Xatcm08/dxS8MKvhTNMaHd6a4fqDGWQOB6JBLXGhGgs=
=VvRm
-----END PGP SIGNATURE-----

--eqBhlv20JJinRjet--