qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@redhat.com>,
	Cole Robinson <crobinso@redhat.com>,
	libvirt-list@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] Introduce a -libvirt-caps flag as a stop-gap
Date: Tue, 27 Jul 2010 10:41:57 -0700	[thread overview]
Message-ID: <20100727174157.GE7474@x200.localdomain> (raw)
In-Reply-To: <4C4F0B6C.2030804@codemonkey.ws>

* Anthony Liguori (anthony@codemonkey.ws) wrote:
> Here are the possible things we can do:
> 
> 1) merge -libvirt-caps as an intermediate solution, stop caring
> about -help changes, when full caps are introduced, stop updating
> -libvirt-caps
> 
> 2) don't merge -libvirt-caps, stop caring about -help changes, put
> everything on getting full caps merged by 0.14
> 
> 3) don't merge -libvirt-caps, care about making -help changes, use
> -help as the caps mechanism until full caps get merged

3.5) same as 3) + add test case to qemu to test that -help parser from
libvirt isn't busted.

> We can't do (3).  I'm going to revert the -help changes for 0.13 so
> that old versions of libvirt work but not for master.

I suspect that if the breakage is seen, it'd be easy to fix.  Adding new
help items won't be the problem, just the subtle changes to the existing
output.  Suck?  Yes.  Workable until full caps?  Think so.

thanks,
-chris

  parent reply	other threads:[~2010-07-27 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 15:55 [Qemu-devel] [PATCH] Introduce a -libvirt-caps flag as a stop-gap Anthony Liguori
2010-07-27 16:09 ` [Qemu-devel] " Daniel P. Berrange
2010-07-27 16:38   ` Anthony Liguori
2010-07-27 17:00     ` Daniel P. Berrange
2010-07-27 17:20       ` Anthony Liguori
2010-07-28  9:53         ` Daniel P. Berrange
2010-07-28 13:44           ` Anthony Liguori
2010-07-27 17:41     ` Chris Wright [this message]
2010-07-28  4:52     ` Avi Kivity
2010-07-28  8:57 ` [Qemu-devel] " Amit Shah

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=20100727174157.GE7474@x200.localdomain \
    --to=chrisw@redhat.com \
    --cc=anthony@codemonkey.ws \
    --cc=crobinso@redhat.com \
    --cc=libvirt-list@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).