From: Nick Alcock <nick.alcock@oracle.com>
To: binutils@sourceware.org
Cc: Mike Frysinger <vapier@gmail.com>
Subject: Re: [PATCH] libctf: delete unused libctf_TEXINFOS
Date: Thu, 10 Feb 2022 13:59:19 +0000 [thread overview]
Message-ID: <87y22irfew.fsf@esperi.org.uk> (raw)
In-Reply-To: <Yeyi7Ulph7RibR16@vapier> (Mike Frysinger via Binutils's message of "Sat, 22 Jan 2022 19:35:57 -0500")
On 23 Jan 2022, Mike Frysinger via Binutils verbalised:
> ping ... i'll prob push it in a bit as semi-obvious since the generated
> code is not affected by its removal.
Looks good.
> -mike
>
> On 01 Dec 2021 23:44, Mike Frysinger via Binutils wrote:
>> It's not clear what this was meant for, but it's not used by anything,
>> and the info pages still generate fine without it.
It's code residue that I stopped using before committing any of this,
and didn't notice I'd left behind. Thanks for cleaning it up!
prev parent reply other threads:[~2022-02-10 13:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 4:44 Mike Frysinger
2022-01-23 0:35 ` Mike Frysinger
2022-02-10 13:59 ` Nick Alcock [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=87y22irfew.fsf@esperi.org.uk \
--to=nick.alcock@oracle.com \
--cc=binutils@sourceware.org \
--cc=vapier@gmail.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).