From: Paolo Bonzini <pbonzini@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
"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>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Anthony PERARD" <anthony.perard@citrix.com>,
"Samuel Thibault" <samuel.thibault@ens-lyon.org>,
"Alex Bennée" <alex.bennee@linaro.org>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] Maintainers, please git-am -m
Date: Fri, 8 Feb 2019 18:18:26 +0100 [thread overview]
Message-ID: <80f10fa7-d283-d97d-7f08-2372beb9ed7b@redhat.com> (raw)
In-Reply-To: <21d093b7-d414-f049-6dbc-e15af138ca8f@redhat.com>
On 08/02/19 17:07, Philippe Mathieu-Daudé wrote:
> And yet this isn't a pull request but a simple patch, so the Message-Id
> might not be very relevant there.
Yes, I agree that Message-Id is not that relevant if you're taking a
patch from someone else and then reposting it. But it's a relatively
rare case when >1 people are collaborating on revisions of a series.
Paolo
next prev parent reply other threads:[~2019-02-08 17:18 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 [this message]
2019-02-25 16:13 ` Eric Blake
2019-02-26 7:15 ` Markus Armbruster
2019-02-26 14:14 ` Eric Blake
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=80f10fa7-d283-d97d-7f08-2372beb9ed7b@redhat.com \
--to=pbonzini@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=philmd@redhat.com \
--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).