From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Mark Salter <msalter@redhat.com>, libc-ports@sourceware.org, hp@axis.com
Subject: Re: glibc am33 and cris architectures
Date: Mon, 26 Mar 2012 17:10:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1203261707270.17052@digraph.polyomino.org.uk> (raw)
In-Reply-To: <orr4wtnp8g.fsf@livre.localdomain>
On Fri, 16 Mar 2012, Alexandre Oliva wrote:
> I've long been out of touch WRT am33, but I finally brought this up
> within Red Hat folks that are involved with it.
>
> Mark Salter volunteered to contribute the updates he'd worked on, but
> that had failed to be contributed because I failed to review the TLS
> support patches for GCC and binutils (sorry)
>
> So, instead of removing the port, I suggest we name Mark maintainer of
> the am33 port. Any objections?
I haven't seen any objections; obviously some pretty large patches will be
needed to bring the port up to date, replace the Linuxthreads port by an
NPTL port and generally update sysdeps files for several years of libc
changes that involve all-targets updates, so they are in sync with the
libc versions again. And then he'll need to keep a watch on libc commits
for any that require am33 updates to keep am33 in sync, and make such
updates to the port as and when such libc commits are made.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-03-26 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-21 15:21 Joseph S. Myers
2012-02-21 17:24 ` Hans-Peter Nilsson
2012-02-21 17:36 ` Joseph S. Myers
2012-03-16 4:29 ` Alexandre Oliva
2012-03-26 17:10 ` Joseph S. Myers [this message]
2012-03-27 13:34 ` Mark Salter
2012-05-21 23:30 ` Joseph S. Myers
2012-05-22 13:24 ` Mark Salter
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=Pine.LNX.4.64.1203261707270.17052@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=aoliva@redhat.com \
--cc=hp@axis.com \
--cc=libc-ports@sourceware.org \
--cc=msalter@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).