From: "Alex Bennée" <alex.bennee@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Stefan Hajnoczi" <stefanha@redhat.com>
Subject: Re: [PATCH 1/3] docs/code-provenance: clarify scope very early
Date: Mon, 22 Sep 2025 17:05:17 +0100 [thread overview]
Message-ID: <87segemq0y.fsf@draig.linaro.org> (raw)
In-Reply-To: <20250922154843.60233-2-pbonzini@redhat.com> (Paolo Bonzini's message of "Mon, 22 Sep 2025 17:48:40 +0200")
Paolo Bonzini <pbonzini@redhat.com> writes:
> The AI policy in QEMU is not about content generators, it is about generated
> content. Other uses are explicitly not covered. Rename the policy and clarify
> its scope in the TL;DR section, as a matter of convenience to the reader.
>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-09-22 16:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 15:48 [PATCH 0/3] docs/code-provenance: clarify AI exception process Paolo Bonzini
2025-09-22 15:48 ` [PATCH 1/3] docs/code-provenance: clarify scope very early Paolo Bonzini
2025-09-22 15:55 ` Peter Maydell
2025-09-22 16:05 ` Alex Bennée [this message]
2025-09-23 17:58 ` Stefan Hajnoczi
2025-09-22 15:48 ` [PATCH 2/3] docs/code-provenance: make the exception process more prominent Paolo Bonzini
2025-09-23 17:58 ` Stefan Hajnoczi
2025-09-23 19:20 ` Paolo Bonzini
2025-09-23 20:00 ` Stefan Hajnoczi
2025-09-22 15:48 ` [PATCH 3/3] docs/code-provenance: AI exceptions are in addition to DCO Paolo Bonzini
2025-09-22 15:54 ` Peter Maydell
2025-09-23 17:59 ` Stefan Hajnoczi
2025-09-29 7:54 ` Kevin Wolf
2025-09-29 9:19 ` Paolo Bonzini
2025-09-29 9:35 ` Kevin Wolf
2025-09-29 15:10 ` Paolo Bonzini
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=87segemq0y.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).