From: Miroslav Rezanina <mrezanin@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Qemu-block <qemu-block@nongnu.org>,
QEMU Trivial <qemu-trivial@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] qemu-doc: Do not hard-code the name of the QEMU binary
Date: Tue, 14 Jan 2020 09:52:41 -0500 (EST) [thread overview]
Message-ID: <1592123957.1925031.1579013561355.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAFEAcA_Y83T1n6q6sJoc9JSDGGqtGbnaAJuavuBon5rTepxw=Q@mail.gmail.com>
----- Original Message -----
> From: "Peter Maydell" <peter.maydell@linaro.org>
> To: "Thomas Huth" <thuth@redhat.com>
> Cc: "QEMU Developers" <qemu-devel@nongnu.org>, "Paolo Bonzini" <pbonzini@redhat.com>, "QEMU Trivial"
> <qemu-trivial@nongnu.org>, "Miroslav Rezanina" <mrezanin@redhat.com>, "Eduardo Habkost" <ehabkost@redhat.com>,
> "Qemu-block" <qemu-block@nongnu.org>, "Richard Henderson" <rth@twiddle.net>
> Sent: Tuesday, January 14, 2020 3:34:22 PM
> Subject: Re: [Qemu-devel] [PATCH] qemu-doc: Do not hard-code the name of the QEMU binary
>
> On Wed, 28 Aug 2019 at 10:37, Thomas Huth <thuth@redhat.com> wrote:
> >
> > In our documentation, we use a mix of "$QEMU", "qemu-system-i386" and
> > "qemu-system-x86_64" when we give examples to the users how to run
> > QEMU. Some more consistency would be good here. Also some distributions
> > use different names for the QEMU binary (e.g. "qemu-kvm" in RHEL), so
> > providing more flexibility here would also be good. Thus let's define
> > some variables for the names of the QEMU command and use those in the
> > documentation instead: @value{qemu_system} for generic examples, and
> > @value{qemu_system_x86} for examples that only work with the x86
> > binaries.
> >
> > Signed-off-by: Thomas Huth <thuth@redhat.com>
> > ---
> > docs/qemu-block-drivers.texi | 72 ++++++++++----------
> > docs/qemu-cpu-models.texi | 10 +--
> > qemu-doc.texi | 81 +++++++++++-----------
> > qemu-options.hx | 128 +++++++++++++++++------------------
> > 4 files changed, 149 insertions(+), 142 deletions(-)
> >
> > diff --git a/docs/qemu-block-drivers.texi b/docs/qemu-block-drivers.texi
> > index c02547e28c..2c7ea49c32 100644
> > --- a/docs/qemu-block-drivers.texi
> > +++ b/docs/qemu-block-drivers.texi
> > @@ -2,6 +2,8 @@
> > QEMU block driver reference manual
> > @c man end
> >
> > +@set qemu_system qemu-system-x86_64
> > +
> > @c man begin DESCRIPTION
> >
> > @node disk_images_formats
> > @@ -405,7 +407,7 @@ QEMU can automatically create a virtual FAT disk image
> > from a
> > directory tree. In order to use it, just type:
> >
> > @example
> > -qemu-system-i386 linux.img -hdb fat:/my_directory
> > +@value{qemu_system} linux.img -hdb fat:/my_directory
> > @end example
>
> Do you use the ability to change the text being substituted
> here downstream ? If so, heads-up that I'm working on a
> conversion of this texi file to rst. I'll put in a
> similar rst substitution-reference, which will look like
> this:
>
> .. |qemu_system| replace:: qemu-system-x86_64
>
> but you'll need to update your downstream processes if
> you're changing the value in the texi currently.
>
Yes we are using it and it make our changes much more simple.
Mirek
> thanks
> -- PMM
>
>
--
Miroslav Rezanina
Software Engineer - Virtualization Team Maintainer
prev parent reply other threads:[~2020-01-14 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 9:34 [Qemu-devel] [PATCH] qemu-doc: Do not hard-code the name of the QEMU binary Thomas Huth
2019-08-28 19:18 ` [Qemu-devel] [Qemu-block] " John Snow
2019-08-29 5:41 ` Thomas Huth
2019-08-29 17:29 ` John Snow
2019-08-30 8:03 ` [Qemu-devel] " Miroslav Rezanina
2020-01-14 14:34 ` Peter Maydell
2020-01-14 14:52 ` Miroslav Rezanina [this message]
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=1592123957.1925031.1579013561355.JavaMail.zimbra@redhat.com \
--to=mrezanin@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@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).