From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: [PATCH v2] Autoconf: add variable for pass arbitrary options to qemu upstream
Date: Tue, 10 Apr 2012 02:53:29 -0700 (PDT) [thread overview]
Message-ID: <1334051609079-5629497.post@n5.nabble.com> (raw)
In-Reply-To: <9641D0F0-4AB5-48DA-9553-55EEED4D1D41@citrix.com>
Thanks for reply, I probably had already done:
http://xen.1045712.n5.nabble.com/PATCH-v3-Added-optional-build-configs-for-qemu-upstream-td5544305.html
but seem to be not good, or I not understand something?
--
View this message in context: http://xen.1045712.n5.nabble.com/PATCH-v2-Autoconf-add-variable-for-pass-arbitrary-options-to-qemu-upstream-tp5617799p5629497.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
prev parent reply other threads:[~2012-04-10 9:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 13:30 [PATCH v2] Autoconf: add variable for pass arbitrary options to qemu upstream Fabio Fantoni
2012-04-04 14:00 ` Roger Pau Monne
2012-04-06 9:01 ` Fantu
2012-04-10 9:31 ` Roger Pau Monne
2012-04-10 9:53 ` Fantu [this message]
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=1334051609079-5629497.post@n5.nabble.com \
--to=fantonifabio@tiscali.it \
--cc=xen-devel@lists.xensource.com \
/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).