[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2364.69.2.248.210.1217954354.squirrel@webmail.wolfmountaingroup.com>
Date: Tue, 5 Aug 2008 10:39:14 -0600 (MDT)
From: jmerkey@...fmountaingroup.com
To: "Chris Friesen" <cfriesen@...tel.com>
Cc: jmerkey@...fmountaingroup.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
> jmerkey@...fmountaingroup.com wrote:
>
>> If you go back to LKML from 2000, this debugger has been around for 10
>> years. I agree not in the hands of the public, but its very mature
>> in comparison to kdb or kgdb.
>
> Without public use, it's difficult to determine that there aren't any
> nasty interactions.
>
> If you want to maximize your chances of getting this code into the
> kernel, you might want to read Jonathan Corbet's post, "[PATCH] A
> development process document, V2". It discusses the normal process, how
> to prepare patches for submission, etc.
>
> Chris
>
Read it already. Quite a few large companies are using it at present and
have been since 2000, BTW.
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