From: Gleb Natapov <gleb@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] specify vmchannel as part of "user" net option
Date: Thu, 15 Jan 2009 22:54:59 +0200 [thread overview]
Message-ID: <20090115205459.GA27165@redhat.com> (raw)
In-Reply-To: <496F9B65.2030102@codemonkey.ws>
On Thu, Jan 15, 2009 at 02:24:05PM -0600, Anthony Liguori wrote:
> Gleb Natapov wrote:
>> To configure vmchannel and something like this to -net user:
>> channels=;777:unix:/tmp/777,server
>>
>
> I'd really like to avoid using ';' as a deliminator. Is the a more
> clever way we can do this without it totally sucking?
>
I can't say I like it, but we can't use ',' and ':' as parsing will be
ambiguous. So what's left?
--
Gleb.
next prev parent reply other threads:[~2009-01-15 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 15:10 [Qemu-devel] [PATCH] specify vmchannel as part of "user" net option Gleb Natapov
2009-01-15 20:24 ` Anthony Liguori
2009-01-15 20:54 ` Gleb Natapov [this message]
2009-01-15 21:27 ` Anthony Liguori
2009-01-15 23:58 ` Daniel P. Berrange
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=20090115205459.GA27165@redhat.com \
--to=gleb@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).