From: Fam Zheng <famz@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [Qemu-devel] [PATCH 0/2] Two small improvements for docker.py
Date: Fri, 14 Jul 2017 14:48:50 +0800 [thread overview]
Message-ID: <20170714064850.GE18687@lemon> (raw)
In-Reply-To: <20170712075528.22770-1-famz@redhat.com>
On Wed, 07/12 15:55, Fam Zheng wrote:
> The first one is a small simplification, the second one is an error handling
> improvement.
>
> Fam Zheng (2):
> docker.py: Drop infile parameter
> docker.py: Improve subprocess exit code handling
Thanks, queued:
https://github.com/famz/qemu/tree/staging
prev parent reply other threads:[~2017-07-14 6:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 7:55 [Qemu-devel] [PATCH 0/2] Two small improvements for docker.py Fam Zheng
2017-07-12 7:55 ` [Qemu-devel] [PATCH 1/2] docker.py: Drop infile parameter Fam Zheng
2017-07-12 11:35 ` Philippe Mathieu-Daudé
2017-07-12 7:55 ` [Qemu-devel] [PATCH 2/2] docker.py: Improve subprocess exit code handling Fam Zheng
2017-07-12 17:16 ` Philippe Mathieu-Daudé
2017-07-14 6:48 ` Fam Zheng [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=20170714064850.GE18687@lemon \
--to=famz@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
/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).