From: Ralf Baechle <ralf@linux-mips.org>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Jim Gifford <maillist@jg555.com>,
Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: GLIBC moved mips to Ports
Date: Tue, 21 Feb 2006 15:33:10 +0000 [thread overview]
Message-ID: <20060221153310.GA28396@linux-mips.org> (raw)
In-Reply-To: <20060221144211.GA19378@nevyn.them.org>
On Tue, Feb 21, 2006 at 09:42:11AM -0500, Daniel Jacobowitz wrote:
> Sigh. Jim, you are slightly misinterpreting this.
>
> MIPS has _never_ been a high priority of the glibc maintainers. What
> happened here is that they admitted it - and moved it to a separate
> repository so that (A) they don't need to deal with it, and (B) people
> who are interested can deal with it. It's unfortunate, but realistic.
>
> The ports repository is going to continue to be supported and we're
> going to keep it working. We just have to do the legwork. I'll go
> over the MIPS build fixes this week sometime.
Great. None of my patches in the past years has even received any sort
of feedback. Maybe time to to look through them again ...
Leave waiting for 386 and gang to move to glibc ports as well.
Ralf
prev parent reply other threads:[~2006-02-21 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 3:54 GLIBC moved mips to Ports Jim Gifford
2006-02-21 14:42 ` Daniel Jacobowitz
2006-02-21 15:33 ` Ralf Baechle [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=20060221153310.GA28396@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=dan@debian.org \
--cc=linux-mips@linux-mips.org \
--cc=maillist@jg555.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.