All of lore.kernel.org
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Git Mailing List <git@vger.kernel.org>,
	"brian m. carlson" <sandals@crustytoothpaste.net>,
	Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] gitk: discourage AI contributions
Date: Sun, 23 Aug 2026 21:10:46 +0800	[thread overview]
Message-ID: <aorxVo_6_U1ceaKm@wyuan.org> (raw)
In-Reply-To: <b4ce8b09-5faa-4e6e-af38-5384a71ae699@kdbg.org>

[+cc Johannes Schindelin]

On Sun, Aug 23, 2026 at 11:25:42AM +0200, Johannes Sixt wrote:
> Since the provenance of code generated by AI cannot be tracked with
> confidence, which would be necessary to sign off a contribution, tell
> contributors not to use AI.
> 
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> ---
>  Following a recent brief discussion[1] it looks like I should not
>  accept code for Gitk that was generated by AI even if the submitter
>  understands all of it. Should I discourage AI contributions outright
>  like this or would it overshoot the mark?
> 
>  -- Hannes
> 
>  [1] https://lore.kernel.org/git/aooRdiVdjovWSFiG@fruit.crustytoothpaste.net/T/#md44580584f30c9b3e3c9e23250baf08b7fd7fb0c

I followed the discussion between Brian and Junio, and I have no
intention of further expanding the discussion about the legal and
technical issues surrounding the use of AI/LLM. However, I would like to
point out that several of dscho's recent commits seem to carry an
Assisted-by trailer, and, unless I missed something (possibly), nobody
appears to have raised the issue or strongly objected to it. Of course,
I believe dscho also fully understood the code he submitted.

(This is getting a little away from the DCO legal issue that Junio and
Brian were discussing.)

So how do we distinguish between "Generated" and "Assisted"? Perhaps the
LLM merely assisted him with some investigative work rather than
actually writing any code.

Meanwhile, in the Linux kernel community, probably the most prominent
user of the DCO, within it, Linus also expressed his views [1] on the
use of LLMs a few weeks ago, while the Linux Foundation has published
guidance on the legal issues surrounding the use of AI. [2]

Although I know that the Git and Linux kernel communities do not follow
exactly the same rules, Jonathan Corbet updated the kernel's
requirements for disclosing LLM use a couple of days ago, namely:

Assisted-by: LLM [TOOL1] [TOOL2]

Perhaps this gives us a way to tell whether a patch contains content
generated by an LLM. (But if we want to ban it entirely, please
disregard this part.)

Thanks,
Weijie

Emm, I´m not sure which thread would be the right place to continue this
discussion, sorry.

[1] https://lore.kernel.org/all/CAHk-=wi4zC+Ze8e+p3tMv8TtG_80KzsZ1syL9anBtmEh5Z40vg@mail.gmail.com/
[2] https://www.linuxfoundation.org/legal/generative-ai

  reply	other threads:[~2026-08-23 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-23  9:25 [PATCH] gitk: discourage AI contributions Johannes Sixt
2026-08-23 13:10 ` Weijie Yuan [this message]
2026-08-26  6:55   ` Weijie Yuan
2026-08-26 21:55 ` brian m. carlson

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=aorxVo_6_U1ceaKm@wyuan.org \
    --to=wy@wyuan.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=johannes.schindelin@gmx.de \
    --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.