From: Stuart Brady <sdbrady@ntlworld.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH][RFC] Handling ':' on filenames
Date: Sun, 8 Mar 2009 11:49:41 +0000 [thread overview]
Message-ID: <20090308114941.GA12649@miranda.arrow> (raw)
In-Reply-To: <49B3ABDF.2080803@redhat.com>
On Sun, Mar 08, 2009 at 01:28:31PM +0200, Uri Lublin wrote:
> b. We do not want to use "qcow2:/tmp/a:b" as filenames (been there).
> We want to use -drive file=/tmp/a:b,format=qcow2 (and
> similar "qemu-img info -f ").
I can't help but feel that any approach to extracting filenames from the
middle of arguments will always have problems.
I suppose a syntax like this:
-drive file=/tmp/file,with,commas:and:colons ,format=qcow2
(i.e. with the next parameter to -drive starting in a new argument)...
wouldn't win many supporters though?
Cheers,
--
Stuart Brady
next prev parent reply other threads:[~2009-03-08 11:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 21:28 [Qemu-devel] [PATCH][RFC] Handling ':' on filenames Eduardo Habkost
2009-03-08 11:28 ` Uri Lublin
2009-03-08 11:49 ` Stuart Brady [this message]
2009-03-09 14:32 ` Eduardo Habkost
2009-03-09 21:11 ` Jamie Lokier
2009-03-09 14:21 ` Eduardo Habkost
2009-03-09 14:27 ` Eduardo Habkost
2009-03-10 3:59 ` 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=20090308114941.GA12649@miranda.arrow \
--to=sdbrady@ntlworld.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).