From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: szabolcs.nagy@arm.com, gdb-patches@sourceware.org, nd@arm.com,
simon.marchi@polymtl.ca, tom@tromey.com
Subject: Re: [committed] Fix gdb.texinfo for old makeinfo (again)
Date: Mon, 15 Jan 2018 13:42:00 -0000 [thread overview]
Message-ID: <877esj6xx0.fsf@redhat.com> (raw)
In-Reply-To: <831sirz2ht.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 15 Jan 2018 15:16:14 +0200")
On Monday, January 15 2018, Eli Zaretskii wrote:
>> From: Sergio Durigan Junior <sergiodj@redhat.com>
>> Cc: gdb-patches@sourceware.org, nd@arm.com, Simon Marchi <simon.marchi@polymtl.ca>, Tom Tromey <tom@tromey.com>, Eli Zaretskii <eliz@gnu.org>
>> Date: Mon, 15 Jan 2018 08:14:39 -0500
>>
>> > * gdb.texinfo (set cwd): Add period.
>> > (gdb-add-index): Move anchor.
>>
>> Thanks for catching this. I confess I don't have makeinfo 4.13
>> installed and didn't think I needed to test generating the docs with it.
>
> Cross-references must have period or comma following them, it's just
> that latest versions of makeinfo are lenient in enforcing that.
Ah, fair enough. Thanks for the explanation, Eli!
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2018-01-15 13:42 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 ` [committed] Fix gdb.texinfo for old makeinfo (again) Eli Zaretskii
2018-01-15 13:14 ` Sergio Durigan Junior
2018-01-15 13:17 ` Eli Zaretskii
2018-01-15 13:42 ` Sergio Durigan Junior [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=877esj6xx0.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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).