All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	patches@linaro.org
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] qemu-options.hx: Improve documentation of chardev multiplexing mode
Date: Tue, 16 Feb 2016 18:57:17 +0100	[thread overview]
Message-ID: <56C362FD.7070008@redhat.com> (raw)
In-Reply-To: <56C3562C.8000503@redhat.com>

On 02/16/16 18:02, Paolo Bonzini wrote:
> 
> 
> On 16/02/2016 17:32, Laszlo Ersek wrote:
>> I'm a big fan of muxing the stdio backend between the (human) monitor
>> and the guest's serial console:
>>
>>   -chardev stdio,signal=off,mux=on,id=char0 \
>>   -mon chardev=char0,mode=readline,default \
>>   -serial chardev:char0 \
> 
> Or just "-serial mon:stdio". :)

For what reason on earth are these three *possible* at all to tie up
into a single command line option?

... I appreciate your teaching me ancient lores, but I think I just died
a little inside.

Laszlo



WARNING: multiple messages have this Message-ID (diff)
From: Laszlo Ersek <lersek@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] qemu-options.hx: Improve documentation of chardev multiplexing mode
Date: Tue, 16 Feb 2016 18:57:17 +0100	[thread overview]
Message-ID: <56C362FD.7070008@redhat.com> (raw)
In-Reply-To: <56C3562C.8000503@redhat.com>

On 02/16/16 18:02, Paolo Bonzini wrote:
> 
> 
> On 16/02/2016 17:32, Laszlo Ersek wrote:
>> I'm a big fan of muxing the stdio backend between the (human) monitor
>> and the guest's serial console:
>>
>>   -chardev stdio,signal=off,mux=on,id=char0 \
>>   -mon chardev=char0,mode=readline,default \
>>   -serial chardev:char0 \
> 
> Or just "-serial mon:stdio". :)

For what reason on earth are these three *possible* at all to tie up
into a single command line option?

... I appreciate your teaching me ancient lores, but I think I just died
a little inside.

Laszlo

  reply	other threads:[~2016-02-16 17:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 16:03 [Qemu-trivial] [PATCH] qemu-options.hx: Improve documentation of chardev multiplexing mode Peter Maydell
2016-02-16 16:03 ` [Qemu-devel] " Peter Maydell
2016-02-16 16:20 ` [Qemu-trivial] " Paolo Bonzini
2016-02-16 16:20   ` [Qemu-devel] " Paolo Bonzini
2016-02-16 16:27 ` [Qemu-trivial] " Eric Blake
2016-02-16 16:27   ` Eric Blake
2016-02-16 16:32 ` [Qemu-trivial] " Laszlo Ersek
2016-02-16 16:32   ` Laszlo Ersek
2016-02-16 17:02   ` [Qemu-trivial] " Paolo Bonzini
2016-02-16 17:02     ` Paolo Bonzini
2016-02-16 17:57     ` Laszlo Ersek [this message]
2016-02-16 17:57       ` Laszlo Ersek
2016-02-16 18:07       ` [Qemu-trivial] " Peter Maydell
2016-02-16 18:07         ` Peter Maydell
2016-02-16 16:36 ` [Qemu-trivial] " Kashyap Chamarthy
2016-02-16 16:36   ` [Qemu-devel] " Kashyap Chamarthy

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=56C362FD.7070008@redhat.com \
    --to=lersek@redhat.com \
    --cc=patches@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.