All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Brauner <brauner@kernel.org>
To: tech-board-discuss@lists.linux.dev
Cc: Christian Brauner <brauner@kernel.org>,
	linux-kernel@vger.kernel.org,
	ksummit-discuss@lists.linuxfoundation.org,
	christianvanbrauner@gmail.com
Subject: LLM based rewrites
Date: Sat,  7 Mar 2026 21:49:20 +0100	[thread overview]
Message-ID: <20260307-clean-room-6118793eb175@brauner> (raw)

Hey,

I believe it is a rite of passage to at least once cause a shouting
match with a non-technical topic.

It seems increasingly viable to rewrite an entire codebase using an LLM
and it currently looks like there's at least some examples as in [1]
where people try to use an LLM based rewrite as a clean-room
implementation to relicense the project. I think the FOSDEM talk at [2]
is related to this as well.

Maybe this is a "let's worry about it later" situation but I wonder
whether this is something that the LF or TAB is actively following.

I'm not asking for a legal analysis. I'm mostly looking for reassurance
that we as the kernel community and our representatives have an eye on
this. I find this quite worrisome.

Fwiw, I was made aware that there's a tangentially related discussion on
the distribution mailing list at [3].

Thanks!
Christian

Link: https://github.com/chardet/chardet/issues/327 [1]
Link: https://github.com/chardet/chardet/releases/tag/7.0.0 [1]
Link: https://fosdem.org/2026/schedule/event/SUVS7G-lets_end_open_source_together_with_this_one_simple_trick [2]
Link: https://lore.kernel.org/a3f792e918674e208492a077679ae6ffc88ce0c9.camel@gentoo.org [3]

             reply	other threads:[~2026-03-07 20:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 20:49 Christian Brauner [this message]
2026-03-09 13:57 ` LLM based rewrites Steven Rostedt
2026-03-09 15:31   ` H. Peter Anvin
2026-03-09 16:16     ` Steven Rostedt
2026-03-09 16:33       ` Jonathan Corbet
2026-03-09 16:55         ` H. Peter Anvin
2026-03-09 17:09           ` H. Peter Anvin
2026-03-09 18:19           ` James Bottomley
2026-03-09 18:34             ` Steven Rostedt
2026-03-09 18:38               ` Dr. David Alan Gilbert
2026-03-09 18:54               ` James Bottomley
2026-03-10  4:52           ` Theodore Tso
     [not found]             ` <CAMTJT3_cVaA7aJmDa6j288-qwP3jzvM_R2pdk+XmE+1U=Sovbg@mail.gmail.com>
2026-03-10 12:47               ` Theodore Tso
2026-03-10 14:10                 ` Dr. Greg
2026-03-09 16:05 ` Dave Hansen
2026-03-09 16:16 ` James Bottomley

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=20260307-clean-room-6118793eb175@brauner \
    --to=brauner@kernel.org \
    --cc=christianvanbrauner@gmail.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tech-board-discuss@lists.linux.dev \
    /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.