From: Elena Ufimtseva <elena.ufimtseva@oracle.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
john.g.johnson@oracle.com,
Stefano Stabellini <sstabellini@kernel.org>,
jag.raman@oracle.com,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
QEMU <qemu-devel@nongnu.org>,
Ross Lagerwall <ross.lagerwall@citrix.com>,
liran.alon@oracle.com, Stefan Hajnoczi <stefanha@redhat.com>,
kanth.ghatraju@oracle.com
Subject: Re: [Qemu-devel] [multiprocess RFC PATCH 00/37] Initial support of multi-process qemu
Date: Fri, 8 Mar 2019 11:49:42 -0800 [thread overview]
Message-ID: <20190308194941.GC20066@heatpipe> (raw)
In-Reply-To: <CAJ+F1CK_Lr+UKkzicLvfwcBRa4kTTrOQTm0wN8cEHek+Tkj=dw@mail.gmail.com>
On Thu, Mar 07, 2019 at 02:27:57PM +0100, Marc-André Lureau wrote:
> Hi
>
> On Thu, Mar 7, 2019 at 11:46 AM Stefan Hajnoczi <stefanha@gmail.com> wrote:
> >
> > On Wed, Mar 06, 2019 at 11:20:25PM -0800, elena.ufimtseva@oracle.com wrote:
> > > From: Elena Ufimtseva <elena.ufimtseva@oracle.com>
> > >
> > > Initial support of multi-process qemu
> >
> > Hi Elena,
> > Please use the following setting when sending future patch series:
> >
> > $ git config sendemail.thread shallow
> >
> > This way all patches are part of a single email thread (starting with
> > your PATCH 00 cover letter). Reviewers find this more convenient so
> > that individual emails don't get separated and lost.
Thanks Stefan, will do.
> >
>
> Please also check that there is no regression after each commit. In
> particular, the build shouldn't fail, so we can easily study, apply
> and bisect patches one by one.
>
Yep, we try to make sure each commit builds and will automate for future
series as well, maybe with some simple tests.
Elena
> thanks
>
>
> --
> Marc-André Lureau
prev parent reply other threads:[~2019-03-08 19:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 7:20 [Qemu-devel] [multiprocess RFC PATCH 00/37] Initial support of multi-process qemu elena.ufimtseva
2019-03-07 7:22 ` [Qemu-devel] [multiprocess RFC PATCH 35/37] multi-process: QMP/HMP commands to resize block device on remote process elena.ufimtseva
2019-03-07 14:11 ` Kevin Wolf
2019-03-07 15:26 ` Dr. David Alan Gilbert
2019-03-07 16:15 ` Eric Blake
2019-03-07 10:45 ` [Qemu-devel] [multiprocess RFC PATCH 00/37] Initial support of multi-process qemu Stefan Hajnoczi
2019-03-07 13:27 ` Marc-André Lureau
2019-03-08 19:49 ` Elena Ufimtseva [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=20190308194941.GC20066@heatpipe \
--to=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=kanth.ghatraju@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=liran.alon@oracle.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=stefanha@gmail.com \
--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 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.