Re: Release sprint results - team changes, auto-rm and arch status

To: debian-devel@lists.debian.org, debian-mips@lists.debian.org
Subject: Re: Release sprint results - team changes, auto-rm and arch status
From: Tollef Fog Heen <tfheen@err.no>
Date: Mon, 02 Dec 2013 08:22:50 +0100
Message-id: <871u1vg1it.fsf@qurzaw.varnish-software.com>
Mail-followup-to: debian-devel@lists.debian.org
In-reply-to: <20131201213355.GA21237@hall.aurel32.net> (Aurelien Jarno's message of "Sun, 1 Dec 2013 22:33:55 +0100")
References: <20131128200456.7097820103F18@thykier.net> <20131129082243.GA9931@hall.aurel32.net> <1385733459.23855.103.camel@deadeye.wl.decadent.org.uk> <20131129141214.GB14719@ohm.rr44.fr> <1385853901.2760.25.camel@deadeye.wl.decadent.org.uk> <20131201213355.GA21237@hall.aurel32.net>

]] Aurelien Jarno 

> Also note that the latest batches of the Loongson-2F CPUs have the bug
> fixed.

That doesn't help us when the MIPS porters seem to be unable to get us
any reasonable machine with the bug fixed, even after repeated
proddings.  IIRC, aba has been poking at this on and off for about six
months, but that doesn't help us until we actually have machines racked
and set up as porter boxes/buildds.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Reply to:

Follow-Ups:
- Re: Release sprint results - team changes, auto-rm and arch status
  - From: Aurelien Jarno <aurelien@aurel32.net>

References:
- Re: Release sprint results - team changes, auto-rm and arch status
  - From: Aurelien Jarno <aurelien@aurel32.net>

Prev by Date: Re: Role of Release Goals
Next by Date: Re: Release sprint results - team changes, auto-rm and arch status
Previous by thread: Re: Release sprint results - team changes, auto-rm and arch status
Next by thread: Re: Release sprint results - team changes, auto-rm and arch status
Index(es):
- Date
- Thread