From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: nd@arm.com, gdb-patches@sourceware.org, 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:25:00 -0000 [thread overview]
Message-ID: <5A5C9DB6.9070306@arm.com> (raw)
In-Reply-To: <83a7xfz5h2.fsf@gnu.org>
On 15/01/18 12:11, Eli Zaretskii wrote:
>> Date: Mon, 15 Jan 2018 11:51:52 +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>
>> now with patch attached.
>
> Hmm... why did you need this one:
>
>> -@pindex gdb-add-index
>
> That's an index entry for gdb-add-index, it should stay, I think.
>
i still get the error if i keep @pindex there,
if i move it together with @anchor below @heading
that works, shall i make that change?
(i just wanted to unbreak the build for our
automated toolchain tests, but there might be
better fix)
next prev parent reply other threads:[~2018-01-15 12:25 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 [this message]
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
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=5A5C9DB6.9070306@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=sergiodj@redhat.com \
--cc=simon.marchi@polymtl.ca \
--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).