From: Michal Novotny <minovotn@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] vl.c: Output error on invalid machine type provided
Date: Tue, 30 Jul 2013 21:10:30 +0200 [thread overview]
Message-ID: <51F80FA6.3050407@redhat.com> (raw)
In-Reply-To: <871u6fvpf9.fsf@blackfin.pond.sub.org>
Hi Markus,
thanks, v3 sent.
Michal
On 07/30/2013 09:05 PM, Markus Armbruster wrote:
> Michal Novotny <minovotn@redhat.com> writes:
>
>> Hi Markus,
>> should I rebase it or no need and can maintainer do it before push?
> Depends on the maintainer :)
>
> I'd respin.
>
--
Michal Novotny <minovotn@redhat.com>, RHCE, Red Hat
Virtualization | libvirt-php bindings | php-virt-control.org
prev parent reply other threads:[~2013-07-30 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 14:54 [Qemu-devel] [PATCH v2] vl.c: Output error on invalid machine type provided Michal Novotny
2013-07-30 15:17 ` Markus Armbruster
2013-07-30 15:30 ` Michal Novotny
2013-07-30 19:05 ` Markus Armbruster
2013-07-30 19:10 ` Michal Novotny [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=51F80FA6.3050407@redhat.com \
--to=minovotn@redhat.com \
--cc=armbru@redhat.com \
--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).