From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Markus Armbruster" <armbru@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, "Daniel P.Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Kevin Wolf" <kwolf@redhat.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
"Alexander Graf" <agraf@csgraf.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [PATCH v3 1/3] docs: introduce dedicated page about code provenance / sign-off
Date: Wed, 4 Jun 2025 09:46:59 +0200 [thread overview]
Message-ID: <37b3f3a1-bacb-4682-a9d2-7771e29fe55f@linaro.org> (raw)
In-Reply-To: <87r000ypi0.fsf@pond.sub.org>
On 4/6/25 08:44, Markus Armbruster wrote:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> Markus Armbruster <armbru@redhat.com> writes:
>>
>>> From: Daniel P. Berrangé <berrange@redhat.com>
>>>
>>> Currently we have a short paragraph saying that patches must include
>>> a Signed-off-by line, and merely link to the kernel documentation.
>>> The linked kernel docs have a lot of content beyond the part about
>>> sign-off an thus are misleading/distracting to QEMU contributors.
>>>
>>> This introduces a dedicated 'code-provenance' page in QEMU talking
>>> about why we require sign-off, explaining the other tags we commonly
>>> use, and what to do in some edge cases.
>>>
>>> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
>>> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
>>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>>> ---
>>> docs/devel/code-provenance.rst | 218 ++++++++++++++++++++++++++++++
>>> docs/devel/index-process.rst | 1 +
>>> docs/devel/submitting-a-patch.rst | 18 +--
>>> 3 files changed, 221 insertions(+), 16 deletions(-)
>>> create mode 100644 docs/devel/code-provenance.rst
>>> +
>>> + Signed-off-by: YOUR NAME <YOUR@EMAIL>
>>> +
>>> +using a known identity (sorry, no anonymous contributions.)
>>> +
>>
>> maybe "(contributions cannot be anonymous)" is more direct?
>
> If we're deviating from the kernel's text (which is *fine*), let's get
> rid of the parenthesis:
>
> using a known identity. Contributions cannot be anonymous.
>
> or in active voice:
>
> using a known identity. We cannot accept anonymous contributions.
I'd add an anchor in the "commonly known identity" paragraph added in
commit 270c81b7d59 and here link to it.
>
> I like this one the best.
next prev parent reply other threads:[~2025-06-04 7:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 14:25 [PATCH v3 0/3] docs: define policy forbidding use of "AI" / LLM code generators Markus Armbruster
2025-06-03 14:25 ` [PATCH v3 1/3] docs: introduce dedicated page about code provenance / sign-off Markus Armbruster
2025-06-03 16:53 ` Alex Bennée
2025-06-04 6:44 ` Markus Armbruster
2025-06-04 7:18 ` Daniel P. Berrangé
2025-06-04 7:46 ` Philippe Mathieu-Daudé [this message]
2025-06-04 8:52 ` Markus Armbruster
2025-06-05 9:04 ` Markus Armbruster
2025-06-04 7:58 ` Gerd Hoffmann
2025-06-05 14:52 ` Markus Armbruster
2025-06-05 15:07 ` Alex Bennée
2025-06-03 14:25 ` [PATCH v3 2/3] docs: define policy limiting the inclusion of generated files Markus Armbruster
2025-06-03 14:25 ` [PATCH v3 3/3] docs: define policy forbidding use of AI code generators Markus Armbruster
2025-06-03 15:37 ` Kevin Wolf
2025-06-04 6:18 ` Markus Armbruster
2025-06-03 18:25 ` Stefan Hajnoczi
2025-06-04 6:17 ` Markus Armbruster
2025-06-04 7:15 ` Daniel P. Berrangé
2025-06-04 7:54 ` Philippe Mathieu-Daudé
2025-06-04 8:40 ` Daniel P. Berrangé
2025-06-04 9:19 ` Philippe Mathieu-Daudé
2025-06-04 9:04 ` Markus Armbruster
2025-06-04 8:58 ` Markus Armbruster
2025-06-04 9:22 ` Daniel P. Berrangé
2025-06-04 9:40 ` Markus Armbruster
2025-06-04 12:35 ` Yan Vugenfirer
2025-06-04 9:10 ` Daniel P. Berrangé
2025-06-04 11:01 ` Stefan Hajnoczi
2025-06-03 15:25 ` [PATCH v3 0/3] docs: define policy forbidding use of "AI" / LLM " 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=37b3f3a1-bacb-4682-a9d2-7771e29fe55f@linaro.org \
--to=philmd@linaro.org \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=stefanha@redhat.com \
--cc=thuth@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).