Linux Documentation
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Christian Brauner <brauner@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jonathan Corbet <corbet@lwn.net>
Cc: Jens Axboe <axboe@kernel.dk>,
	David Hildenbrand <david@kernel.org>,
	Jeff Layton <jlayton@kernel.org>,
	Vlastimil Babka <vbabka@kernel.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH RFC] coding-assistants: simplify attribution
Date: Thu, 2 Jul 2026 12:27:17 +0200	[thread overview]
Message-ID: <7d2ba1b4-6199-406e-88ae-fb5c9fad4689@kernel.org> (raw)
In-Reply-To: <20260701-work-coding-assistants-v1-1-a20a94d1d606@kernel.org>

On 01/07/2026 17:54, Christian Brauner wrote:
> I remain very confused by our coding assistant contribution guidelines.
> I'm going to be a bit polemic now but this seriously in good faith.
> 
> Why precisely do we require all this detailed information about what
> specific coding assistant was used?
> 
> I find it very irritating that our git history has effectively started
> to function a bit like a free advertising platform for a bunch of AI
> companies and their proprietary agents and models.
> 
> And it reamins unclear to me what exactly we do get out of this detailed
> information: Do we want to run statistical analysis on what agent and
> model is used the most and publish that on LWN at some point?
> 
> I acknowledge that my stance is even more radical: imho we would just
> stop it with any disclosure requirements completely. It's useless imho.
> We already see that other than core contributors most people don't care
> and will just not disclose their usage of AI. I think this is entirely
> pointless and worse it brings in undefined legal status as well. It's
> not like recent events of pulling certain models from the face of the
> earth have made this any less concerning.
> 
> But fine, if we want to do this can we please just dumb it down to
> 
> Assisted-by: LLM
> 

Yes, I agree. Useful information would be the model or trained data,
e.g. to judge for any copyright issues, but I doubt anyone will ever
provide such details.

I also see little value to keep even the Assisted-by tag in the first
place. I am interested in seeing named respectable tools in commit msg
as reasons for doing this commit, e.g. I am fixing warning from Smatch
so I mention Smatch. Sashiko fits this purpose as well. I have no
interests to see "Claude" as reason of doing something.

Best regards,
Krzysztof

      parent reply	other threads:[~2026-07-02 10:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 15:54 [PATCH RFC] coding-assistants: simplify attribution Christian Brauner
2026-07-01 16:08 ` Mark Brown
2026-07-02  7:10   ` Christian Brauner
2026-07-01 16:08 ` Jonathan Corbet
2026-07-01 16:12   ` David Hildenbrand (Arm)
2026-07-02  7:11   ` Christian Brauner
2026-07-02  9:51   ` David Disseldorp
2026-07-01 16:10 ` David Hildenbrand (Arm)
2026-07-02  7:27   ` Christian Brauner
2026-07-02  7:46     ` David Hildenbrand (Arm)
2026-07-02  8:10       ` Laurent Pinchart
2026-07-02  8:16         ` David Hildenbrand (Arm)
2026-07-02 10:04       ` Lorenzo Stoakes
2026-07-02  8:08     ` Laurent Pinchart
2026-07-02  8:28       ` Christian Brauner
2026-07-02  9:24   ` Lorenzo Stoakes
2026-07-01 18:35 ` Jeff Layton
2026-07-01 18:53   ` Jakub Kicinski
2026-07-02  7:29     ` Christian Brauner
2026-07-02  7:28   ` Christian Brauner
2026-07-02  8:12 ` Jori Koolstra
2026-07-02  8:44   ` Vlastimil Babka (SUSE)
2026-07-02  9:09     ` Jori Koolstra
2026-07-02  9:39       ` Lorenzo Stoakes
2026-07-02  9:37     ` Lorenzo Stoakes
2026-07-02  9:38     ` Laurent Pinchart
2026-07-02  9:44       ` Lorenzo Stoakes
2026-07-02 10:34     ` Krzysztof Kozlowski
2026-07-02 10:27 ` Krzysztof Kozlowski [this message]

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=7d2ba1b4-6199-406e-88ae-fb5c9fad4689@kernel.org \
    --to=krzk@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=corbet@lwn.net \
    --cc=david@kernel.org \
    --cc=jlayton@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@kernel.org \
    --cc=workflows@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox