From: Alan Modra <amodra@gmail.com>
To: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: bfd_com_section, bfd_abs_section et al.
Date: Sat, 05 May 2012 04:38:00 -0000 [thread overview]
Message-ID: <20120505043818.GB17181@bubble.grove.modra.org> (raw)
In-Reply-To: <20120505032605.GA17181@bubble.grove.modra.org>
On Sat, May 05, 2012 at 12:56:05PM +0930, Alan Modra wrote:
> We've been threatening to get rid of bfd_com_section et al for over 13
> years. This patch does the deed. No real changes here, but this
> should make is easier to, for example, make these sections per-bfd.
Oops, this needs committing too.
* bfd-in2.h: Regenerate.
--
Alan Modra
Australia Development Lab, IBM
prev parent reply other threads:[~2012-05-05 4:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 3:26 Alan Modra
2012-05-05 4:38 ` 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=20120505043818.GB17181@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
/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