[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2832.69.2.248.210.1218142926.squirrel@webmail.wolfmountaingroup.com>
Date: Thu, 7 Aug 2008 15:02:06 -0600 (MDT)
From: jmerkey@...fmountaingroup.com
To: "Daniel Barkalow" <barkalow@...ervon.org>
Cc: jmerkey@...fmountaingroup.com,
"Chris Friesen" <cfriesen@...tel.com>,
"Nick Piggin" <nickpiggin@...oo.com.au>,
"Geert Uytterhoeven" <geert@...ux-m68k.org>,
"Stefan Richter" <stefanr@...6.in-berlin.de>,
"Josh Boyer" <jwboyer@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE] Merkey's Kernel Debugger
> On Tue, 5 Aug 2008, jmerkey@...fmountaingroup.com wrote:
>
>> Read it already. Quite a few large companies are using it at present
>> and
>> have been since 2000, BTW.
>
> The criterion for kernel inclusion isn't really whether it works, however.
> It's whether other people would be able to understand it well enough to
> support it if you disappear (or if somebody else has changes that require
> changes to it). If it works well but isn't nice code, nobody really
> benefits from having it in the kernel distribution rather than external
> (like it's been for the past 8 years). If it is nice code (somewhat
> regardless of whether it happens to work right now), people can work on it
> and keep it in sync with the kernel as they change things.
>
> -Daniel
> *This .sig left intentionally blank*
>
It both works and is nice code. But I may not be impartial.
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists