All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qdev merge plans?
Date: Tue, 14 Jul 2009 17:25:20 -0500	[thread overview]
Message-ID: <4A5D05D0.4030004@codemonkey.ws> (raw)
In-Reply-To: <4A5CFD47.7050803@redhat.com>

Gerd Hoffmann wrote:
>   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?

Early in your series, you introduce -device.  But -device syntax doesn't 
seem to be resolved yet.

I don't think it's appropriate to pull in -device this close to the 
feature freeze when the command line syntax is still being debated.  You 
only countered Paul's suggestions this morning so I don't think there's 
any indication that this discussion has converged yet.

Quite a lot of your queue consists of things you've only posted as 
Proof-of-concept series (like qdev/isa).

So let me ask you, what is the set of patches that you think is 
non-contended, posted as a non-RFC, but not yet merged?

Regards,

Anthony Liguori

  reply	other threads:[~2009-07-14 22:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14 21:48 [Qemu-devel] qdev merge plans? Gerd Hoffmann
2009-07-14 22:25 ` Anthony Liguori [this message]
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=4A5D05D0.4030004@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.