From: Mark Salter <msalter@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-ports@sourceware.org, Mike Frysinger <vapier@gentoo.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Richard Henderson <rth@twiddle.net>,
"Carlos O'Donell" <carlos@systemhalted.org>
Subject: Re: Ports state for 2.16 regarding global changes
Date: Fri, 15 Jun 2012 16:18:00 -0000 [thread overview]
Message-ID: <1339777097.32384.35.camel@deneb.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1206151550000.4869@digraph.polyomino.org.uk>
On Fri, 2012-06-15 at 15:52 +0000, Joseph S. Myers wrote:
> * am33: generally massively out of date and I have not tried to
> identify specific changes needed.
I have been working on getting this updated. ATM, I'm blocked waiting on
a fix for a bug in the gcc patch adding am33 tls support. I expect to be
past this sometime next week so I can actually start testing things.
Would it be helpful to go ahead and post the glibc patches now or wait
until I get them tested?
--Mark
next prev parent reply other threads:[~2012-06-15 16:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 15:53 Joseph S. Myers
2012-06-15 16:18 ` Mark Salter [this message]
2012-06-15 16:41 ` Joseph S. Myers
2012-06-15 17:28 ` Richard Henderson
2012-06-15 18:56 ` Joseph S. Myers
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=1339777097.32384.35.camel@deneb.redhat.com \
--to=msalter@redhat.com \
--cc=carlos@systemhalted.org \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=rth@twiddle.net \
--cc=schwab@linux-m68k.org \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).