From: "Alex Bennée" <alex.bennee@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
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>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"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: Thu, 05 Jun 2025 16:07:57 +0100 [thread overview]
Message-ID: <87msam5ir6.fsf@draig.linaro.org> (raw)
In-Reply-To: <87sekeckba.fsf@pond.sub.org> (Markus Armbruster's message of "Thu, 05 Jun 2025 16:52:25 +0200")
Markus Armbruster <armbru@redhat.com> writes:
> Markus Armbruster <armbru@redhat.com> writes:
>
>> Alex Bennée <alex.bennee@linaro.org> writes:
>
> [...]
>
>>> We don't mention the Link: or Message-Id: tags.
>>
>> Yes, but should it go into code-provenance.rst or
>> submitting-a-patch.rst?
>>
>> You asked for guidance on use of "Message-Id:" in your review of v2. I
>> understand the practice, and can write guidance, but I wanted to get
>> this out before my vacation next week, so I left it for later, as
>> mentioned in the cover letter.
>>
>> How do we use "Link:"? What about "Closes:"?
>
> I didn't address this in v4. I could try in a later revision, but I'd
> prefer to do it on top.
Sure - no problem.
>
> [...]
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-06-05 15:08 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é
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 [this message]
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=87msam5ir6.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=agraf@csgraf.de \
--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=philmd@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 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.