From: Anthony Liguori <aliguori@cs.utexas.edu>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] Escape filenames in monitor
Date: Sun, 17 Dec 2006 10:36:59 -0600 [thread overview]
Message-ID: <4585722B.1040907@cs.utexas.edu> (raw)
In-Reply-To: <200612171541.42717.jseward@acm.org>
Julian Seward wrote:
> On Saturday 16 December 2006 21:11, Anthony Liguori wrote:
>
>> info block is impossible to parse reliably because there is no escaping
>> done on the filename.
>>
>
> Don't you also need to convert \ to \\ ? Else any \ which was in
> the original string will confuse the parser of the escaped output.
>
Yup, you are correct. Thanks!
Regards,
Anthony Liguori
> J
>
>
> _______________________________________________
> Qemu-devel mailing list
> Qemu-devel@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
next prev parent reply other threads:[~2006-12-17 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 21:03 [Qemu-devel] [PATCH 0/2] Make the monitor a bit more program-friendly Anthony Liguori
2006-12-16 21:11 ` [Qemu-devel] [PATCH 1/2] Escape filenames in monitor Anthony Liguori
2006-12-17 15:41 ` Julian Seward
2006-12-17 16:36 ` Anthony Liguori [this message]
2006-12-16 21:15 ` [Qemu-devel] [PATCH 2/2] Reinitialize monitor upon reconnect Anthony Liguori
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=4585722B.1040907@cs.utexas.edu \
--to=aliguori@cs.utexas.edu \
--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).