From: Eric Blake <eblake@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Cc: "Marc-André Lureau" <mlureau@redhat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16
Date: Tue, 17 Jan 2017 11:05:27 -0600 [thread overview]
Message-ID: <d8e5834e-c1ee-cfa1-c6dd-1cf5f0dcd027@redhat.com> (raw)
In-Reply-To: <87h94x99e4.fsf@dusky.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On 01/17/2017 06:08 AM, Markus Armbruster wrote:
>
> Three possible solutions, in increasing order of complexity:
>
> 1. Live with the warning from old versions. If a new version comes
> around that does something with @subtitle, it'll just work.
>
> 2. Suppress the warning with @iftex-hammer. No change in output now.
> If a new version comes around that does something with @subtitle, we
> won't profit unless we take out the @iftex.
>
> 3. Replace -D by @set, either by preprocessing .texi, or by including a
> generated snippet. No change in output now. If a new version comes
> around that does something with @subtitle, it'll just work.
Automake projects use option 3 - they create version.texi with @set
commands, then @include that into the main file. Should be fairly easy
to crib the makefile magic from an autotooled project if you want to go
that option.
>
> My order of preference is aligned with decreasing complexity, i.e. first
> 1., then 2., then 3.
I'm fine with any of the options (3 is nicest, but also the most work).
I do agree, however, that if we are going to include version information
(which I find useful), then we want it in both pdf and html outputs.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
prev parent reply other threads:[~2017-01-17 17:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 9:33 [Qemu-devel] [PULL v2 000/180] QAPI patches for 2017-01-16 Markus Armbruster
2017-01-16 15:58 ` Peter Maydell
2017-01-17 8:31 ` Markus Armbruster
2017-01-17 9:54 ` Marc-André Lureau
2017-01-17 10:13 ` Markus Armbruster
2017-01-17 11:08 ` Peter Maydell
2017-01-17 12:08 ` Markus Armbruster
2017-01-17 12:24 ` Peter Maydell
2017-01-17 13:24 ` Markus Armbruster
2017-01-17 13:59 ` Peter Maydell
2017-01-17 14:15 ` Marc-André Lureau
2017-01-17 14:23 ` Markus Armbruster
2017-01-17 16:43 ` Peter Maydell
2017-01-20 14:39 ` Peter Maydell
2017-01-20 15:46 ` Markus Armbruster
2017-01-20 15:48 ` Peter Maydell
2017-01-23 12:48 ` Alex Bennée
2017-01-23 13:59 ` Daniel P. Berrange
2017-01-23 14:49 ` Markus Armbruster
2017-01-24 9:53 ` Markus Armbruster
2017-01-24 10:03 ` Peter Maydell
2017-01-24 11:08 ` Markus Armbruster
2017-01-24 10:09 ` Markus Armbruster
2017-01-24 10:49 ` Paolo Bonzini
2017-01-17 17:05 ` Eric Blake [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=d8e5834e-c1ee-cfa1-c6dd-1cf5f0dcd027@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=mlureau@redhat.com \
--cc=peter.maydell@linaro.org \
--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).