From: Mike Frysinger <vapier@gentoo.org>
To: "Carlos O'Donell" <carlos@systemhalted.org>
Cc: "linux-parisc" <linux-parisc@vger.kernel.org>,
Debian HPPA Port List <debian-hppa@lists.debian.org>,
Gentoo HPPA <gentoo-hppa@lists.gentoo.org>
Subject: Re: Removing HPPA Linuxthreads support in glibc-ports.
Date: Thu, 20 Oct 2011 16:31:50 -0400 [thread overview]
Message-ID: <201110201631.52046.vapier@gentoo.org> (raw)
In-Reply-To: <CADZpyiwAqDmsb4TLCwo0KGBm9c_Y1P9iLir8gXJBOJPOTiRr4g@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 338 bytes --]
On Thursday 20 October 2011 14:55:46 Carlos O'Donell wrote:
> I plan to remove all HPPA Linuxthreads support from glibc-ports.
>
> The support is well past bit-rotten.
>
> Is anyone opposed to this?
guess we don't have much choice since it's been purged from the core. but
nptl support isn't mainlined yet right ? :/
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-10-20 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 18:55 Removing HPPA Linuxthreads support in glibc-ports Carlos O'Donell
2011-10-20 20:31 ` Mike Frysinger [this message]
2011-10-20 20:35 ` Carlos O'Donell
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=201110201631.52046.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=carlos@systemhalted.org \
--cc=debian-hppa@lists.debian.org \
--cc=gentoo-hppa@lists.gentoo.org \
--cc=linux-parisc@vger.kernel.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