From: Anthony Liguori <aliguori@linux.vnet.ibm.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Staging tree updated with patches I'm considering for 0.12.0
Date: Fri, 18 Dec 2009 08:25:54 -0600 [thread overview]
Message-ID: <4B2B90F2.4070306@linux.vnet.ibm.com> (raw)
In-Reply-To: <m3k4wkhiyg.fsf@crossbow.pond.sub.org>
Markus Armbruster wrote:
> Commit 731b9ff6 is correct, but commit 24598d23 is more general, and it
> comes first. Drop it the former?
>
> "Nice to have" commit log corrections:
>
> * 92375e10 qdev: Improve uni-north device names (was: [Qemu-devel] [FOR 0.12 PATCH] qdev: Replace device names containing whitespace)
>
> The (was: ...) part is ugly. My fault. Would be nice to strip it.
>
> * 249dbde8 fix vga names in default_list
>
> Body of commit message is factually incorrect. It says:
>
> markus has changed vga names recently and forgot to adapt default_list.
>
> The commit fixes up commit 64465297, which went in *after* the name
> change in commit 556cd098. So it's technically a mismerge.
>
Heh, sure, I can update those logs.
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-12-18 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 21:53 [Qemu-devel] Staging tree updated with patches I'm considering for 0.12.0 Anthony Liguori
2009-12-18 6:52 ` Markus Armbruster
2009-12-18 14:25 ` Anthony Liguori [this message]
2009-12-18 7:30 ` [Qemu-devel] " Jan Kiszka
2009-12-18 14:27 ` Anthony Liguori
2009-12-18 9:04 ` [Qemu-devel] " Gerd Hoffmann
2009-12-18 14:27 ` Anthony Liguori
2009-12-18 9:06 ` Gerd Hoffmann
2009-12-18 11:48 ` Gerd Hoffmann
2009-12-18 14:19 ` Anthony Liguori
[not found] ` <m3zl5gqz73.fsf@neno.neno>
2009-12-18 14:20 ` [Qemu-devel] " Anthony Liguori
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=4B2B90F2.4070306@linux.vnet.ibm.com \
--to=aliguori@linux.vnet.ibm.com \
--cc=armbru@redhat.com \
--cc=kraxel@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).