All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: Jim Gifford <maillist@jg555.com>
Cc: Linux MIPS List <linux-mips@linux-mips.org>
Subject: Re: GLIBC moved mips to Ports
Date: Tue, 21 Feb 2006 09:42:11 -0500	[thread overview]
Message-ID: <20060221144211.GA19378@nevyn.them.org> (raw)
In-Reply-To: <43FA8F04.3040606@jg555.com>

On Mon, Feb 20, 2006 at 07:54:44PM -0800, Jim Gifford wrote:
> Just an FYI, I've been working trying to keep MIPS updated in glibc. 
> Again some changes were made that broke the MIPS build with the current 
> snapshot. I guess all of Daniel's and my work just got thrown away. As 
> of today MIPS is no longer going to be support in trunk. Here's the 
> message I received today.
> 
> In my opinion this seems to mean that MIPS is not a high priority in 
> their book.
> 
> ------- Additional Comments From roland at gnu dot org  2006-02-21 02:14 
> -------
> For the trunk, mips has moved to the ports repository.
> Daniel should be able to commit his fixes there directly.
> Items needing merge in the 2.3 branch can be reassigned to me.

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.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2006-02-21 14:35 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 [this message]
2006-02-21 15:33   ` Ralf Baechle

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=20060221144211.GA19378@nevyn.them.org \
    --to=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.