From: Gerd Hoffmann <kraxel@redhat.com>
To: aliguori@codemonkey.ws
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] qdev merge plans?
Date: Tue, 14 Jul 2009 23:48:55 +0200 [thread overview]
Message-ID: <4A5CFD47.7050803@redhat.com> (raw)
Hi Anthony,
Your queue continues bitrotting. BlueSwirl did more qdev conversions
with the result that more fixups are needed to make the tree build again
once your queue is pushed ...
For now I did incremental fixups and didn't change the patches you have
queued up already. At least for the build failure this isn't ideal
though as it leaves a few revisions which don't build which is bad for
bisecting.
So what is your plan to handle the mess^H^H^H^Hmerge?
I plan to respin my patches tomorrow and can adjust the patches the way
you want to have it.
cheers,
Gerd
PS: complete patch queue (including work-in-progress bits) is at
http://git.et.redhat.com/?p=qemu-kraxel.git;a=shortlog;h=refs/heads/qdev.v11
next reply other threads:[~2009-07-14 21:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 21:48 Gerd Hoffmann [this message]
2009-07-14 22:25 ` [Qemu-devel] qdev merge plans? Anthony Liguori
2009-07-15 6:21 ` Gerd Hoffmann
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=4A5CFD47.7050803@redhat.com \
--to=kraxel@redhat.com \
--cc=aliguori@codemonkey.ws \
--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).