From: Augusto César Radtke <radtke@conectiva.com>
To: "Jeremy M. Dolan" <jmd@foozle.turbogeek.org>
Cc: Matthias Juchem <juchem@uni-mannheim.de>, linux-kernel@vger.kernel.org
Subject: Re: Bug reporting script? (was: removal of redundant line in documentation)
Date: Sat, 6 Jan 2001 15:40:27 -0200 [thread overview]
Message-ID: <20010106154027.A1461@conectiva.com> (raw)
In-Reply-To: <01010607054600.01947@gandalf> <20010106075402.A3377@foozle.turbogeek.org>
In-Reply-To: <20010106075402.A3377@foozle.turbogeek.org>; from jmd@foozle.turbogeek.org on Sat, Jan 06, 2001 at 07:54:02AM -0600
Jeremy M. Dolan wrote:
> If ver_linux can take off one of those steps, why not include a script
> which takes care of ALL the leg work? All of the files it asks the
> reporter to include are o+r...
>
> I can whip up a bug_report script to walk the user though all of the
> steps in REPORTING-BUGS, if the list isn't averse to 'dumbing down'
> the process to the point where maybe some people who shouldn't be
> submiting bugs (two words: 'user error') end up not being scared off
> by the process.
>
About bug reports, isn't a good thing introduce the sgi's lkcd (linux kernel crash dump) into the main stream of 2.5? The main problem of lkcd in 2.2 was the lack of kiobufs.
I think it as a good thing, for distributions, the distribution guys have the vmlinuz image of the distro, so when a bug happens the user only needs to send the crash dump to the distribution kernel hacker, and he can discuss the bug on lkml.
This introduce a new kind of bug reporter, if the distribution makes avalaible every new development kernel as a package, a user can download and use, crash and report the bug without any knowledge about kernel. So the marketing guys can say: 'help the development of linux without hacking, report bugs'.
Comments?
Augusto
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-06 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 5:51 [PATCHlet]: removal of redundant line in documentation Matthias Juchem
2001-01-06 13:54 ` Bug reporting script? (was: removal of redundant line in documentation) Jeremy M. Dolan
2001-01-06 12:33 ` Matthias Juchem
2001-01-08 23:45 ` Pavel Machek
2001-01-10 19:05 ` Matthias Juchem
2001-01-11 8:58 ` Pavel Machek
2001-01-06 17:40 ` Augusto César Radtke [this message]
2001-01-06 22:19 ` db
2001-01-07 1:21 ` Bug reporting script? Matthias Juchem
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=20010106154027.A1461@conectiva.com \
--to=radtke@conectiva.com \
--cc=jmd@foozle.turbogeek.org \
--cc=juchem@uni-mannheim.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.