public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Carlo Marcelo Arenas Belon
	<carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: [RFC] modular dependencies for kvm's qemu
Date: Tue, 16 Oct 2007 17:34:25 +0200	[thread overview]
Message-ID: <4714DA01.3090808@qumranet.com> (raw)
In-Reply-To: <20071016153603.GB15903@tapir>

Carlo Marcelo Arenas Belon wrote:
>
>> If so I prefer being closer to qemu as you suggest.
>>     
>
> you mean closer as on using the same syntax, or closer as on avoiding changing
> qemu unless absolutely needed?
>
>   

Both.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

  reply	other threads:[~2007-10-16 15:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-16  9:22 [RFC] modular dependencies for kvm's qemu Carlo Marcelo Arenas Belon
2007-10-16 10:38 ` Avi Kivity
2007-10-16 13:39 ` Daniel P. Berrange
     [not found]   ` <20071016133930.GB2107-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-10-16 14:21     ` Carlo Marcelo Arenas Belon
2007-10-16 14:20       ` Avi Kivity
     [not found]         ` <4714C8B5.60104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-10-16 14:54           ` Anthony Liguori
2007-10-16 15:36           ` Carlo Marcelo Arenas Belon
2007-10-16 15:34             ` Avi Kivity [this message]
2007-10-16 15:48             ` Anthony Liguori
2007-10-17 14:43             ` Carlo Marcelo Arenas Belon

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=4714DA01.3090808@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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