From: Alan Modra <amodra@bigpond.net.au>
To: binutils@sources.redhat.com
Subject: 2.16.1 candidate patches
Date: Tue, 10 May 2005 00:30:00 -0000 [thread overview]
Message-ID: <20050510002812.GS782@bubble.grove.modra.org> (raw)
In-Reply-To: <20050509211527.GA15861@nevyn.them.org>
On Mon, May 09, 2005 at 05:15:27PM -0400, Daniel Jacobowitz wrote:
> I've checked this in to HEAD and the 2.16 branch. I don't know if
> there will be a binutils 2.16.1; if no other problems turn up in the
> next month or two, probably not. But if there is, it will include ths
> fix.
I'm putting http://sources.redhat.com/ml/binutils/2005-05/msg00340.html
and http://sources.redhat.com/ml/binutils/2005-04/msg00007.html plus
http://sources.redhat.com/ml/binutils/2005-04/msg00121.html on the
branch too. The first one is important enough to roll 2.16.1 for
powerpc64 (or at least anyone using 2.16 and gcc-3.4 on powerpc64 will
want the patch). I'm an idiot because I had a problem report in early
April but discounted it because I couldn't reproduce it, forgetting that
my local gcc-3.4 was patched to not use dot-syms. The other two patches
just got forgotten but aren't critical in any way.
--
Alan Modra
IBM OzLabs - Linux Technology Centre
next prev parent reply other threads:[~2005-05-10 0:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 10:11 [PATCH] Fix make -jN in bfd/doc Gwenole Beauchesne
2005-05-06 13:17 ` Daniel Jacobowitz
2005-05-06 13:57 ` H. J. Lu
2005-05-06 14:13 ` Daniel Jacobowitz
2005-05-06 19:59 ` Daniel Jacobowitz
2005-05-06 22:25 ` Gwenole Beauchesne
2005-05-09 22:09 ` Daniel Jacobowitz
2005-05-10 0:30 ` Alan Modra [this message]
2005-05-10 1:21 ` 2.16.1 candidate patches The Doctor
2005-05-10 1:44 ` Alan Modra
2005-05-10 10:20 ` The Doctor
2005-05-11 0:28 ` Alan Modra
2005-05-11 1:08 ` The Doctor
2005-05-10 1:47 ` Mike Frysinger
2005-05-17 20:39 ` Daniel Jacobowitz
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=20050510002812.GS782@bubble.grove.modra.org \
--to=amodra@bigpond.net.au \
--cc=binutils@sources.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).