On Tue, Oct 17, 2006 at 10:27:50AM -0700, Thomas Bushnell BSG wrote: > I don't care either way whether m68k is released in etch. But I do > care that etch isn't screwed because of a desperate attempt to support > m68k in it. [...] > m68k, while the actual porting team manifestly does not have the > personnel or the time to do the job.
If you have no fucking clue as to what the current state of things is and why the architecture has been thrown out, I suggest you keep your petty comments to yourself. * Etch isn't screwed because of a desperate attempt to support m68k in it, never has been, and never will be. In fact, m68k is screwed (partially) because of a (desperate or not) attempt to preserve etch. * The problem that made us not make etch involves much, much more than either personnel or time. -- <Lo-lan-do> Home is where you have to wash the dishes. -- #debian-devel, Freenode, 2004-09-22 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
