From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
mark.syms@citrix.com, qemu-devel@nongnu.org,
xen-devel@lists.xenproject.org, sstabellini@kernel.org,
anthony@xenproject.org, paul@xen.org, edgar.iglesias@gmail.com
Subject: Re: [BUG] hw/xen: features published after InitWait since 240cc11369fc
Date: Fri, 11 Sep 2026 16:54:09 +0100 [thread overview]
Message-ID: <aqQkIa-l0MyAoUmt@redhat.com> (raw)
In-Reply-To: <CAFEAcA9WAARKjyim9HkYWQA9L45L27NNhxvCVw6CkH5d9pgiYw@mail.gmail.com>
On Fri, Sep 11, 2026 at 03:56:22PM +0100, Peter Maydell wrote:
> On Fri, 11 Sept 2026 at 15:39, David Woodhouse <dwmw2@infradead.org> wrote:
> > I wasn't *actually* setting out to comment on the AI policy today — in
> > fact I didn't really have a strong opinion on it. I spend enough of my
> > life tilting at windmills *intentionally*; this wasn't meant to be one
> > of them.
snip
> Yes. I view that email as pretty strong data for 'even a policy
> shift which says "we're OK with accepting some kinds of AI
> generated code" should still be pretty strong on "text intended
> for humans to read (docs, commit messages, mailing list posts, etc)
> should be written by humans"'. I think that review commentary on
> Paolo's RFC about a less strict policy tended to be in that direction,
> so I don't think I'm completely out on a limb here.
The latest proposed policy explicitly forbids sending AI text
to people:
https://lists.gnu.org/archive/html/qemu-devel/2026-09/msg00260.html
[quote]
### No AI-written text must reach maintainers
These rules apply when publishing AI-assisted work to GitLab or the mailing
list:
- **AI-written cover letters and commit messages are banned**. These are
easy to recognize and waste reviewers' time.
- **AI-generated responses to reviewer comments are banned**. This undermines
the human-to-human interaction fundamental to code review.
- **AI-written issue ("work item") descriptions or comments are banned**. These
are verbose and waste triagers' time.
[/quote]
With regards,
Daniel
--
|: https://berrange.com ~~ https://hachyderm.io/@berrange :|
|: https://libvirt.org ~~ https://entangle-photo.org :|
|: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
next prev parent reply other threads:[~2026-09-11 15:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-11 10:08 [BUG] hw/xen: features published after InitWait since 240cc11369fc Mark Syms
2026-09-11 10:08 ` Mark Syms via qemu development
2026-09-11 12:31 ` David Woodhouse
2026-09-11 13:00 ` Peter Maydell
2026-09-11 13:16 ` David Woodhouse
2026-09-11 14:34 ` David Woodhouse
2026-09-11 14:56 ` Peter Maydell
2026-09-11 15:45 ` David Woodhouse
2026-09-11 15:54 ` Daniel P. Berrangé [this message]
2026-09-12 12:50 ` David Woodhouse
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=aqQkIa-l0MyAoUmt@redhat.com \
--to=berrange@redhat.com \
--cc=anthony@xenproject.org \
--cc=dwmw2@infradead.org \
--cc=edgar.iglesias@gmail.com \
--cc=mark.syms@citrix.com \
--cc=paul@xen.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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.