From: Andrew Morton <akpm@osdl.org>
To: piet@bluelane.com, vgoyal@in.ibm.com,
George Anzinger <george@wildturkeyranch.net>,
Discussion "list for crash utility usage,
maintenance and development" <crash-utility@redhat.com>,
kgdb-bugreport@lists.sourceforge.net,
Subhachandra Chandra <schandra@bluelane.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel.
Date: Wed, 30 Aug 2006 15:57:10 -0700 [thread overview]
Message-ID: <20060830155710.5865faa0.akpm@osdl.org> (raw)
In-Reply-To: <20060830144822.3b8ffb9a.akpm@osdl.org>
On Wed, 30 Aug 2006 14:48:22 -0700
Andrew Morton <akpm@osdl.org> wrote:
> Plus: I'd want to see a maintainance person or team who
> respond promptly to email and who remain reasonably engaged with what's
> going on in the mainline kernel. Because if problems crop up (and they
> will), I don't want to have to be the bunny who has to worry about them...
umm, clarification needed here.
No criticism of the present maintainers intended! Last time I grabbed the
kgdb patches from sf.net they applied nicely, worked quite reliably (much
better than the old ones I'd been trying to sustain) and had been
tremendously cleaned up.
But if we're to move this work from sf.net to kernel.org, the kgdb
maintainers' workload, email load, turnaround time requirements,
bug-difficulty and everything else will go up quite a lot, at least short-term.
If they don't want to volunteer take that on (perfectly legit and sane) then
things should stay as they are.
(otoh, a merge would decrease their patch-maintenance load, and would
increase the number of people who fix things for them, and might attract new
maintainers).
It's a big step.
next prev parent reply other threads:[~2006-08-30 22:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44EC8CA5.789286A@redhat.com>
[not found] ` <20060824111259.GB22145@in.ibm.com>
[not found] ` <44EDA676.37F12263@redhat.com>
[not found] ` <1156966522.29300.67.camel@piet2.bluelane.com>
[not found] ` <20060830204032.GD30392@in.ibm.com>
2006-08-30 21:41 ` Piet Delaney
2006-08-30 21:48 ` Andrew Morton
2006-08-30 22:57 ` Andrew Morton [this message]
2006-08-31 2:42 ` How about an enumerated list of issues with the existing kgdb patches? Piet Delaney
2006-08-31 3:00 ` Andrew Morton
2006-12-13 8:32 ` Piet Delaney
2006-08-30 21:53 ` [RFC] [Crash-utility] Patch to use gdb's bt in crash - works great with kgdb! - KGDB in Linus Kernel Randy.Dunlap
2006-08-30 22:22 ` Piet Delaney
2006-08-31 14:07 ` Andi Kleen
2006-08-31 14:20 ` [Kgdb-bugreport] " Tom Rini
2006-08-31 14:43 ` Andi Kleen
2006-08-31 20:41 ` Piet Delaney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060830155710.5865faa0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=crash-utility@redhat.com \
--cc=george@wildturkeyranch.net \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@bluelane.com \
--cc=schandra@bluelane.com \
--cc=vgoyal@in.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome