From: Laszlo Ersek <lersek@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: "Eric Blake" <eblake@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
qemu-devel@nongnu.org, libvir-list@redhat.com
Subject: Re: [Qemu-devel] [RFC] Defining firmware (OVMF, et al) metadata format & file
Date: Mon, 9 Apr 2018 17:32:41 +0200 [thread overview]
Message-ID: <25fb31d4-0ba4-a827-59f5-76f838a36f8b@redhat.com> (raw)
In-Reply-To: <20180409090244.GP9903@paraplu>
On 04/09/18 11:02, Kashyap Chamarthy wrote:
> - It also provides a persistent command history in a convenient file:
> '~/.qmp-shell_history'
I noticed it used readline, but I didn't know about the dedicated
history file. Nice! Thanks!
Laszlo
next prev parent reply other threads:[~2018-04-09 15:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 14:49 [Qemu-devel] [RFC] Defining firmware (OVMF, et al) metadata format & file Kashyap Chamarthy
2018-03-07 15:18 ` Daniel P. Berrangé
2018-03-08 7:52 ` Gerd Hoffmann
2018-03-08 10:17 ` Daniel P. Berrangé
2018-04-06 17:28 ` Laszlo Ersek
2018-04-06 18:10 ` Eric Blake
2018-04-06 18:21 ` Laszlo Ersek
2018-04-09 9:02 ` Kashyap Chamarthy
2018-04-09 15:32 ` Laszlo Ersek [this message]
2018-03-09 10:02 ` Kashyap Chamarthy
2018-03-08 7:45 ` Gerd Hoffmann
2018-03-08 10:16 ` Daniel P. Berrangé
2018-03-08 11:10 ` Laszlo Ersek
2018-03-08 15:47 ` Daniel P. Berrangé
2018-03-08 20:47 ` Laszlo Ersek
2018-03-09 11:27 ` Kashyap Chamarthy
2018-03-09 15:09 ` Laszlo Ersek
2018-03-12 11:17 ` Daniel P. Berrangé
2018-03-09 14:27 ` Gerd Hoffmann
2018-03-09 15:18 ` Laszlo Ersek
2018-03-12 11:13 ` Daniel P. Berrangé
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=25fb31d4-0ba4-a827-59f5-76f838a36f8b@redhat.com \
--to=lersek@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=kchamart@redhat.com \
--cc=kraxel@redhat.com \
--cc=libvir-list@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).