From: Tom Tromey <tom@tromey.com>
To: binutils@sourceware.org
Cc: Nick Clifton <nickc@redhat.com>
Subject: [RFC 0/2] Allow ancient versions of makeinfo
Date: Wed, 30 Aug 2023 10:26:31 -0600 [thread overview]
Message-ID: <20230830162836.2257576-1-tom@tromey.com> (raw)
This short series tries to fix PR 30703, where old versions of
makeinfo don't work for BFD. I think the underlying cause is that the
BFD doc comments (and/or chew) haven't kept up with how texinfo is
expected to work. However, it seemed most straightforward to just
revert the offending patch.
Let me know what you think. I don't have the old makeinfo so I don't
actually know whether this patch is sufficient.
Tom
next reply other threads:[~2023-08-30 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 16:26 Tom Tromey [this message]
2023-08-30 16:26 ` [RFC 1/2] Revert "Simplify @node use in BFD documentation" Tom Tromey
2023-08-30 22:44 ` Alan Modra
2023-08-30 16:26 ` [RFC 2/2] Remove libbfd.texi Tom Tromey
2023-08-30 22:46 ` Alan Modra
2023-08-30 22:56 ` Alan Modra
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=20230830162836.2257576-1-tom@tromey.com \
--to=tom@tromey.com \
--cc=binutils@sourceware.org \
--cc=nickc@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 read-only IMAP folder(s) and NNTP newsgroup(s).