From: "Alex Bennée" <alex.bennee@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Fabiano Rosas" <farosas@suse.de>,
"Kevin Wolf" <kwolf@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Warner Losh" <imp@bsdimp.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Paolo Bonzini" <bonzini@gnu.org>
Subject: Re: [PATCH v2] docs/devel: relax policy on AI-generated contributions
Date: Thu, 04 Jun 2026 11:04:25 +0100 [thread overview]
Message-ID: <87qzmmsjti.fsf@draig.linaro.org> (raw)
In-Reply-To: <aiBwWH8iirdw9kw7@redhat.com> ("Daniel P. Berrangé"'s message of "Wed, 3 Jun 2026 19:20:08 +0100")
Daniel P. Berrangé <berrange@redhat.com> writes:
> On Wed, Jun 03, 2026 at 07:14:02PM +0100, Alex Bennée wrote:
>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>
>> > Hi Daniel,
>> >
>> > Thanks for the review. It will take a while to incorporate everything
>> > and I'll wait for more feedback, in the meantime just a couple things
>> > I can confirm or add...
>>
>> I mean you could just let the LLM handle it ;-)
>>
>> AI-used-for: collecting comments and updating patch
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>>
>> I only include this by way of an experiment. I think the new text does
>> cover the discussion although I think it has taken a fair amount of
>> verbatim text from the source messages that were commentary rather than
>> suggestions.
>
> Most importantly it has applied no critical thought to the review
> comments, seemingly treated them all as mostly equally important
> and incorporated them. The resulting text is more volumous than
> Paolo's, has poor structure and in places is verging on what I'd
> class as slop.
Well there is no "thought", although its pretty good at text extraction
from the mailing thread. I guess that's the "attention" part of the
model.
It wasn't helped by the fact there was a full lift and shift of the AI
section to a new document. In my other experiments with documentation
I've let the model do the changes and then I can review each hunk and
reword as I go.
For code changes I've found it pretty good - enough so that it might
replace my hand-rolled mechanism for saving review comments:
https://github.com/stsquad/my-emacs-stuff/blob/master/my-org.el#L176
>
>
> With regards,
> Daniel
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2026-06-04 10:04 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 9:46 [PATCH v2] docs/devel: relax policy on AI-generated contributions Paolo Bonzini
2026-05-29 11:52 ` Alex Bennée
2026-05-29 13:06 ` Paolo Bonzini
2026-05-29 13:10 ` Michael S. Tsirkin
2026-05-29 11:59 ` BALATON Zoltan
2026-05-29 15:34 ` Peter Maydell
2026-05-29 15:46 ` Michael S. Tsirkin
2026-05-29 15:55 ` Peter Maydell
2026-05-29 16:17 ` Paolo Bonzini
2026-05-29 17:47 ` Michael S. Tsirkin
2026-06-02 7:38 ` Michael S. Tsirkin
2026-06-02 8:09 ` Paolo Bonzini
2026-06-02 15:53 ` Stefan Hajnoczi
2026-06-03 11:35 ` Paolo Bonzini
2026-06-03 14:55 ` Stefan Hajnoczi
2026-06-03 14:59 ` Daniel P. Berrangé
2026-06-03 15:06 ` Michael S. Tsirkin
2026-06-03 15:35 ` Paolo Bonzini
2026-06-03 17:54 ` Daniel P. Berrangé
2026-06-04 10:37 ` Paolo Bonzini
2026-06-05 9:17 ` Daniel P. Berrangé
2026-06-05 9:25 ` Michael S. Tsirkin
2026-06-05 9:39 ` Daniel P. Berrangé
2026-06-05 9:48 ` Michael S. Tsirkin
2026-06-05 10:23 ` Daniel P. Berrangé
2026-06-05 10:28 ` Michael S. Tsirkin
2026-06-05 10:34 ` Daniel P. Berrangé
2026-06-05 11:26 ` Paolo Bonzini
2026-06-05 12:39 ` BALATON Zoltan
2026-06-05 13:00 ` Daniel P. Berrangé
2026-06-03 18:14 ` Alex Bennée
2026-06-03 18:20 ` Daniel P. Berrangé
2026-06-04 10:04 ` Alex Bennée [this message]
2026-06-04 6:08 ` Michael S. Tsirkin
2026-06-05 10:12 ` Kevin Wolf
2026-06-05 10:23 ` Michael S. Tsirkin
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=87qzmmsjti.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=balaton@eik.bme.hu \
--cc=berrange@redhat.com \
--cc=bonzini@gnu.org \
--cc=farosas@suse.de \
--cc=imp@bsdimp.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@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.