From: Paolo Bonzini <pbonzini@redhat.com>
To: bharata@linux.vnet.ibm.com
Cc: Kevin Wolf <kwolf@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
quintela@redhat.com, qemu-devel <qemu-devel@nongnu.org>,
"Richard W.M. Jones" <rjones@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>
Subject: Re: [Qemu-devel] KVM call agenda for September 25th
Date: Tue, 25 Sep 2012 17:37:22 +0200 [thread overview]
Message-ID: <5061CFB2.8060701@redhat.com> (raw)
In-Reply-To: <20120925153359.GB23071@in.ibm.com>
Il 25/09/2012 17:33, Bharata B Rao ha scritto:
>>> qemu -device \
>>> > > isa-serial,index=0,chr=tcp://localhost:1025/?server=on&wait=off
>> >
>> > Your examples kind of prove this: They aren't much shorter than what
>> > exists today, but they contain ? and &, which are nasty characters on
>> > the command line.
> Right. '&' can't even be specified directly on command line since that will
> result in qemu command being treated as a background job with anything after
> '&' being discarded. I realized that '&' needs to be escaped as %26.
No, %26 is escaped at the URL level, i.e. it doesn't start a new
argumnt. If you need to pass '&' in the shell, simply use quoting or
write it \&.
Paolo
next prev parent reply other threads:[~2012-09-25 15:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 11:28 [Qemu-devel] KVM call agenda for September 25th Juan Quintela
2012-09-24 11:48 ` Paolo Bonzini
2012-09-25 12:13 ` Richard W.M. Jones
2012-09-25 12:57 ` Anthony Liguori
2012-09-25 13:05 ` Richard W.M. Jones
2012-09-25 13:14 ` Luiz Capitulino
2012-09-25 13:30 ` Paolo Bonzini
2012-09-25 14:51 ` Kevin Wolf
2012-09-25 15:33 ` Bharata B Rao
2012-09-25 15:37 ` Paolo Bonzini [this message]
2012-09-25 19:42 ` Anthony Liguori
2012-09-26 7:10 ` Markus Armbruster
2012-09-25 13:27 ` Luiz Capitulino
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=5061CFB2.8060701@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=bharata@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=rjones@redhat.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).