From: Eli Zaretskii <eliz@gnu.org>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: gdb-patches@sourceware.org, nd@arm.com, sergiodj@redhat.com,
simon.marchi@polymtl.ca, tom@tromey.com
Subject: Re: [committed] Fix gdb.texinfo for old makeinfo (again)
Date: Mon, 15 Jan 2018 12:12:00 -0000 [thread overview]
Message-ID: <83bmhvz5k6.fsf@gnu.org> (raw)
In-Reply-To: <5A5C9504.4060001@arm.com> (message from Szabolcs Nagy on Mon, 15 Jan 2018 11:48:20 +0000)
> Date: Mon, 15 Jan 2018 11:48:20 +0000
> From: Szabolcs Nagy <szabolcs.nagy@arm.com>
> CC: nd@arm.com, Sergio Durigan Junior <sergiodj@redhat.com>,
> Simon Marchi <simon.marchi@polymtl.ca>,
> Tom Tromey <tom@tromey.com>, Eli Zaretskii <eliz@gnu.org>
>
> With old makeinfo (version 4.13) the changes introduced in
>
> commit ba643918cf869fa0d064d733f69b453b6fe642ea
> Author: Sergio Durigan Junior <sergiodj@redhat.com>
>
> Install and generate docs for gdb-add-index
>
> fail to build with
>
> gdb/doc/gdb.texinfo:2498: warning: `.' or `,' must follow @xref, not `@'.
> gdb/doc/gdb.texinfo:2517: warning: `.' or `,' must follow @xref, not `@'.
> gdb/doc/gdb.texinfo:43443: Node `gdb-add-index man' requires a sectioning command (e.g., @unnumberedsubsec).
> gdb/doc/gdb.texinfo:43443: `gdb-add-index man' has no Up field (perhaps incorrect sectioning?).
> gdb/doc/gdb.texinfo:43350: Next field of node `gdbinit man' not pointed to (perhaps incorrect sectioning?).
> gdb/doc/gdb.texinfo:43443: This node (gdb-add-index man) has the bad Prev.
>
> This patch fixes the warnings too.
> Committed as obvious.
Thanks.
next prev parent reply other threads:[~2018-01-15 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 11:49 Szabolcs Nagy
2018-01-15 11:52 ` Szabolcs Nagy
2018-01-15 12:12 ` Eli Zaretskii
2018-01-15 12:25 ` Szabolcs Nagy
2018-01-15 12:59 ` Eli Zaretskii
2018-01-15 13:32 ` [committed] Fix gdb.texinfo more Szabolcs Nagy
2018-01-15 12:12 ` Eli Zaretskii [this message]
2018-01-15 13:14 ` [committed] Fix gdb.texinfo for old makeinfo (again) Sergio Durigan Junior
2018-01-15 13:17 ` Eli Zaretskii
2018-01-15 13:42 ` Sergio Durigan Junior
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=83bmhvz5k6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=sergiodj@redhat.com \
--cc=simon.marchi@polymtl.ca \
--cc=szabolcs.nagy@arm.com \
--cc=tom@tromey.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 read-only IMAP folder(s) and NNTP newsgroup(s).