From: Alan Modra <amodra@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: binutils@sourceware.org
Subject: Re: [RFC 2/2] Remove libbfd.texi
Date: Thu, 31 Aug 2023 08:26:49 +0930 [thread overview]
Message-ID: <ZO/JMerpOs6m71DG@squeak.grove.modra.org> (raw)
In-Reply-To: <ZO/G3ZBqGFJgnpYh@squeak.grove.modra.org>
On Thu, Aug 31, 2023 at 08:16:53AM +0930, Alan Modra wrote:
> On Wed, Aug 30, 2023 at 10:26:33AM -0600, Tom Tromey wrote:
> > While paging through the BFD manual, I noticed that the "Internals"
> > node is completely empty. This patch removes it.
> >
> > bfd/ChangeLog
> > 2023-08-30 Tom Tromey <tom@tromey.com>
> >
> > * doc/local.mk (DOCFILES): Remove libbfd.texi.
> > * Makefile.in: Regenerate.
> > * doc/bfd.texi (Internal): Remove node.
>
> Please don't commit this one. We ought to be getting some info,
> starting with the bfd_malloc description. I'll see if I can figure
> out why chew is misbehaving.
It's a makefile problem with pattern rules in bfd/doc/local.mk.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2023-08-30 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 16:26 [RFC 0/2] Allow ancient versions of makeinfo Tom Tromey
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 [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=ZO/JMerpOs6m71DG@squeak.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--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).