From: Luiz Capitulino <lcapitulino@redhat.com>
To: Seiji Aguchi <seiji.aguchi@hds.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Tomoki Sekiyama <tomoki.sekiyama@hds.com>,
"armbru@redhat.com" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] Convert stderr message calling error_get_pretty() to error_report()
Date: Tue, 13 Aug 2013 16:33:51 -0400 [thread overview]
Message-ID: <20130813163351.36b41136@redhat.com> (raw)
In-Reply-To: <A5ED84D3BB3A384992CBB9C77DEDA4D443E82DF8@USINDEM103.corp.hds.com>
On Tue, 13 Aug 2013 20:27:15 +0000
Seiji Aguchi <seiji.aguchi@hds.com> wrote:
> Luiz,
>
> Can you pick up to your tree?
Yes, this is queued for review for 1.7. I should start reviewing patches
for 1.7 in the end of this week or in the beginning of next week.
next prev parent reply other threads:[~2013-08-13 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 19:40 [Qemu-devel] [PATCH v2] Convert stderr message calling error_get_pretty() to error_report() Seiji Aguchi
2013-08-07 19:09 ` Laszlo Ersek
2013-08-13 20:27 ` Seiji Aguchi
2013-08-13 20:33 ` Luiz Capitulino [this message]
2013-08-19 19:38 ` Luiz Capitulino
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=20130813163351.36b41136@redhat.com \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seiji.aguchi@hds.com \
--cc=tomoki.sekiyama@hds.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).