From: Alan Modra <amodra@gmail.com>
To: Pedro Alves <palves@redhat.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 0/5] Rename a few internal symbols to avoid collisions
Date: Fri, 17 Feb 2017 01:06:00 -0000 [thread overview]
Message-ID: <20170217010608.GR3731@bubble.grove.modra.org> (raw)
In-Reply-To: <1487290680-24260-1-git-send-email-palves@redhat.com>
On Fri, Feb 17, 2017 at 12:17:55AM +0000, Pedro Alves wrote:
> bfd: Rename read_{signed,unsigned}_leb128, safe_read_leb128
> bfd: Rename real_{ftell, fseek, fopen}
> bfd: Rename warn_deprecated
> bfd: Rename bsd_write_armap and coff_write_armap
> bfd: Rename Chunk and S3Forced
OK, thanks.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2017-02-17 1:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 0:18 Pedro Alves
2017-02-17 0:18 ` [PATCH 3/5] bfd: Rename warn_deprecated Pedro Alves
2017-02-17 0:18 ` [PATCH 1/5] bfd: Rename read_{signed,unsigned}_leb128, safe_read_leb128 Pedro Alves
2017-02-17 0:18 ` [PATCH 2/5] bfd: Rename real_{ftell, fseek, fopen} Pedro Alves
2017-02-17 0:24 ` [PATCH 4/5] bfd: Rename bsd_write_armap and coff_write_armap Pedro Alves
2017-02-17 0:24 ` [PATCH 5/5] bfd: Rename Chunk and S3Forced Pedro Alves
2017-02-17 1:06 ` Alan Modra [this message]
2017-02-17 2:16 ` [PATCH 0/5] Rename a few internal symbols to avoid collisions Pedro Alves
2017-02-17 2:30 ` Pedro Alves
2017-02-17 2:53 ` 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=20170217010608.GR3731@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=palves@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).