All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>,
	"Alistair Francis" <alistair.francis@wdc.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>,
	"Kevin Wolf" <kwolf@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Warner Losh" <imp@bsdimp.com>, "Paolo Bonzini" <bonzini@gnu.org>
Subject: Re: [PATCH] docs/devel: relax policy on AI-generated contributions
Date: Thu, 28 May 2026 04:18:35 -0400	[thread overview]
Message-ID: <20260528041241-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CABgObfbq9rFNHLYnhbr=5Gn9iJW1-BDsxTMLOjAoeM3h5Ct6wA@mail.gmail.com>

On Thu, May 28, 2026 at 10:04:40AM +0200, Paolo Bonzini wrote:
> On Thu, May 28, 2026 at 9:59 AM Michael S. Tsirkin <mst@redhat.com> wrote:
> > > > > +     AI-used-for: tests, docs
> > > > > +     AI-used-for: code
> > > > > +     AI-used-for: code (refactoring)
> > > > > +     AI-used-for: code (prototype)
> > > > > +     AI-used-for: research
> >
> > BTW: commit log ?
> 
> I don't think I want to encourage it to the point that it requires
> highlighting, quite the opposite in fact. Using AI for minor edits is
> irrelevant, while writing the bulk of the commit message should be a
> conscious act of the submitter.
> 
> This was also mentioned in the other thread.
> 
> > > I suppose it can still be useful for traceability. I copied it from
> > > Kevin's proposal but I can remove it.
> > >
> > > "Research" may also include using a script written by the LLM, which
> > > is encouraged in the first section.
> >
> > but again, if the script is not merged, then the boundaries do not
> > apply?
> 
> See the first sentence above re. traceability and copying from Kevin's
> proposal. :)
> 
> Paolo

OK. It's all nitpicking on my side, anyway.

-- 
MST



  reply	other threads:[~2026-05-28  8:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  7:34 [PATCH] docs/devel: relax policy on AI-generated contributions Paolo Bonzini
2026-05-28  7:40 ` Philippe Mathieu-Daudé
2026-05-28  7:43   ` Paolo Bonzini
2026-05-28  7:50     ` Michael S. Tsirkin
2026-05-28  7:48 ` Michael S. Tsirkin
2026-05-28  7:53   ` Paolo Bonzini
2026-05-28  7:59     ` Michael S. Tsirkin
2026-05-28  8:04       ` Paolo Bonzini
2026-05-28  8:18         ` Michael S. Tsirkin [this message]
2026-05-28  8:26 ` Philippe Mathieu-Daudé
2026-05-28  9:04 ` Alex Bennée
2026-05-28 12:12 ` BALATON Zoltan
2026-05-28 13:45   ` Michael S. Tsirkin
2026-05-28 13:18 ` Fabiano Rosas

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=20260528041241-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=alistair.francis@wdc.com \
    --cc=berrange@redhat.com \
    --cc=bonzini@gnu.org \
    --cc=imp@bsdimp.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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 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.