From: "Michael S. Tsirkin" <mst@redhat.com>
To: Manos Pitsidianakis <manos.pitsidianakis@linaro.org>
Cc: BALATON Zoltan <balaton@eik.bme.hu>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Hajnoczi, Stefan" <stefanha@redhat.com>
Subject: Re: on ai generated and code provenance
Date: Tue, 26 May 2026 09:00:01 -0400 [thread overview]
Message-ID: <20260526085923-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CAAjaMXYzNUG2KNWkOdH8Y5HV18MwxTVR2jVNPaP_m72VZb2P+w@mail.gmail.com>
On Tue, May 26, 2026 at 03:37:50PM +0300, Manos Pitsidianakis wrote:
> On Tue, May 26, 2026 at 3:31 PM Michael S. Tsirkin <mst@redhat.com> wrote:
> >
> > On Tue, May 26, 2026 at 01:27:40PM +0200, BALATON Zoltan wrote:
> > > Maybe clarifying this in the policy could be
> > > done although there will always be people who ignore documents.
> >
> > One advantage of the linux style tags is that at least they differ
> > from whatever ai's put in by default. So whoever does it can get
> > banned pretty quickly.
> >
>
> What would be the mechanism for that though? Getting the list
> administrators involved to ban email addresses from the list?
maintainers learning to ignore patches from bad actors works well enough.
> If banning is to be a deterrent, the process and rules should be
> codified in the docs so that it exists as a warning and there is
> little room for abuse and ambiguity in both sides.
>
> >
>
> --
> Manos Pitsidianakis
> Emulation and Virtualization Engineer at Linaro Ltd
next prev parent reply other threads:[~2026-05-26 13:02 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-24 12:42 on ai generated and code provenance Michael S. Tsirkin
2026-05-24 17:06 ` Alex Bennée
2026-05-24 17:42 ` Michael S. Tsirkin
2026-05-24 18:26 ` Warner Losh
2026-05-24 20:04 ` Michael S. Tsirkin
2026-05-24 20:11 ` Michael S. Tsirkin
2026-05-24 20:44 ` Stefan Hajnoczi
2026-05-25 15:27 ` Stefan Hajnoczi
2026-05-25 16:32 ` Paolo Bonzini
2026-05-25 17:15 ` Warner Losh
2026-05-25 19:44 ` Stefan Hajnoczi
2026-05-25 22:36 ` Michael S. Tsirkin
2026-05-26 13:16 ` Stefan Hajnoczi
2026-05-25 19:56 ` Paolo Bonzini
2026-05-26 21:48 ` Philippe Mathieu-Daudé
2026-05-26 8:23 ` Peter Maydell
2026-05-26 9:28 ` Alex Bennée
2026-05-26 9:57 ` Paolo Bonzini
2026-05-26 11:27 ` BALATON Zoltan
2026-05-26 12:30 ` Michael S. Tsirkin
2026-05-26 12:37 ` Manos Pitsidianakis
2026-05-26 13:00 ` Michael S. Tsirkin [this message]
2026-05-26 13:22 ` Stefan Hajnoczi
2026-05-26 14:01 ` Warner Losh
2026-05-27 7:11 ` Philippe Mathieu-Daudé
2026-05-26 17:43 ` Kevin Wolf
2026-05-26 18:03 ` Michael S. Tsirkin
2026-05-26 18:59 ` Kevin Wolf
2026-05-26 19:30 ` Michael S. Tsirkin
2026-05-26 19:52 ` Warner Losh
2026-05-27 8:41 ` Kevin Wolf
2026-05-27 10:01 ` Paolo Bonzini
2026-05-27 10:43 ` Alex Bennée
2026-05-27 12:49 ` Kevin Wolf
2026-05-27 10:53 ` Kevin Wolf
2026-05-27 12:33 ` Paolo Bonzini
2026-05-27 12:43 ` Michael S. Tsirkin
2026-05-27 10:54 ` Alistair Francis
2026-05-27 14:21 ` Warner Losh
2026-05-28 1:59 ` Alistair Francis
2026-05-28 5:06 ` Michael S. Tsirkin
2026-05-28 7:32 ` Paolo Bonzini
2026-05-27 14:11 ` Michael S. Tsirkin
2026-05-27 14:14 ` Warner Losh
2026-05-27 14:51 ` Kevin Wolf
2026-05-27 16:41 ` Michael S. Tsirkin
2026-05-27 16:50 ` Kevin Wolf
2026-05-27 16:56 ` Michael S. Tsirkin
2026-05-27 17:06 ` Michael S. Tsirkin
2026-05-27 17:15 ` Warner Losh
2026-05-27 17:07 ` Warner Losh
2026-05-27 16:05 ` Paolo Bonzini
2026-05-27 16:48 ` Michael S. Tsirkin
2026-05-27 16:57 ` Warner Losh
2026-05-27 17:05 ` Michael S. Tsirkin
2026-05-27 17:48 ` Paolo Bonzini
2026-05-27 16:39 ` Michael S. Tsirkin
2026-05-26 19:50 ` Michael S. Tsirkin
2026-05-27 7:44 ` Kevin Wolf
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=20260526085923-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=manos.pitsidianakis@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.