Hi Thorsten,
Thorsten Glaser wrote:
> what are we going to do now? The Debian Project has apparently
> given up on m68k citing lack of progress
I don't think it's safe to assume Steve was speaking for the
project as a whole in the message you quoted.
> (
Jonathan Nieder dixit:
>In the far long term, I wonder if something like [1] will be needed to
>bring the port back to the mainstream.
The ColdFire MMU port, yes (especially when they can share
binaries). That would be nice, too.
But let’s do one step at a time, I guess.
bye,
//mirabilos
--
I've finally got some time and am looking at getting started on helping
with Coldfire V4 and M68K.
Up until 3 years ago I worked for Freescale as the engineer that did the
Coldfire V4 Linux work (547x/548x/5445x). After Freescale closed our
facility here in Utah I moved to a different company
I'm willing to help, and I might be finding myself with a LOT of time on my
hands in about four months, so let me know what you'd like me to work on
and I'll see what I can do.
Jason
On Tue, May 15, 2012 at 6:23 PM, Kurt wrote:
> I've finally got some time and am looking at getting started on h
Sorry, but we don't care. m68k has now missed 3 Debian releases
running. That's over 6 years! We should not continue pandering to the
insane idea that m68k is ever going to release with Debian again. This
package has been RC-buggy since approximately forever and should just
be dropped from the arc
On Tue, 15 May 2012, Thorsten Glaser wrote:
>
> The emile removal was (save me sort of forgetting about it?) mostly
> that: a decision between the small and important things. It turns out
> that Debian wants you to fix the small things and leave the important
> things broken for longer becaus
6 matches
Mail list logo
