From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Palmer Dabbelt" <palmer@sifive.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Max Filippov" <jcmvbkbc@gmail.com>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] Maintainers, please git-am -m
Date: Tue, 26 Feb 2019 08:14:08 -0600 [thread overview]
Message-ID: <5be5ec5d-d95f-1669-0b1a-681065bf0da5@redhat.com> (raw)
In-Reply-To: <871s3vnhq5.fsf@dusky.pond.sub.org>
On 2/26/19 1:15 AM, Markus Armbruster wrote:
>>> The Message-id identifies the patch e-mail. It makes finding the review
>>> thread easier and more reliable. It's also a valid key on Patchew[*].
>>
>> I find the tag valuable enough in later git searches that I don't mind
>> feeding my own patches back through the mailing list to add it (patchew
>> helps with that, of course). But for it to become mandatory, we'd need
>> to enhance scripts/checkpatch.pl to enforce it.
>
> I'm afraid checkpatch is the wrong place. When you submit v1 patches
> for review, there is no Message-id. Even for respins, we don't want
> one. It should be added when patches get applied for real, so the
> commit carries exactly one Message-id, and it refers back to the final
> version on the list.
Indeed, I wasn't thinking about how it would work. checkpatch.pl can
filter for 'PULL' being in a subject line, as that will not affect
normal submissions, but there is no guarantee that it will mesh with the
workflows of the various maintainers.
>
> Two ideas:
>
> * Have Patchew flag pull requests lacking Message-id
Yes, that works, as well as patching Peter's sanity-checking script to
do likewise.
>
> * Admittedly vague: some kind of git pre merge hook magic to make
> git-merge flag missing Message-id
I'm not sure if Peter has his sanity-checker script plugged in via git
hooks or some other way.
https://git.linaro.org/people/peter.maydell/misc-scripts.git/
if someone wants to propose a patch to it.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2019-02-26 14:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 7:30 [Qemu-devel] Maintainers, please git-am -m Markus Armbruster
2019-02-08 7:45 ` Thomas Huth
2019-02-08 10:31 ` Gerd Hoffmann
2019-02-08 8:57 ` Cornelia Huck
2019-02-08 10:34 ` Gerd Hoffmann
2019-02-08 16:07 ` Philippe Mathieu-Daudé
2019-02-08 16:59 ` Markus Armbruster
2019-02-08 17:18 ` Paolo Bonzini
2019-02-25 16:13 ` Eric Blake
2019-02-26 7:15 ` Markus Armbruster
2019-02-26 14:14 ` Eric Blake [this message]
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=5be5ec5d-d95f-1669-0b1a-681065bf0da5@redhat.com \
--to=eblake@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=amarkovic@wavecomp.com \
--cc=anthony.perard@citrix.com \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jcmvbkbc@gmail.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=palmer@sifive.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=samuel.thibault@ens-lyon.org \
--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).