mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Daniel Bonekeeper <thehazard@gmail.com>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
	Adrian Bunk <bunk@stusta.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Automatic Kernel Bug Report
Date: Mon, 10 Jul 2006 10:11:31 +0200	[thread overview]
Message-ID: <20060710081131.GA2251@elf.ucw.cz> (raw)
In-Reply-To: <e1e1d5f40607091327y3db1cbdco89ebdb04cda60ce0@mail.gmail.com>

Hi!

> >> Sometimes the user may be just somebody that just started using linux,
> >> or is in an industry that has nothing related to computers. He doesn't
> >> even know that syslog exists, and even if he did, he could not even
> >> care about it.
> >
> >This user will do whatever his distro tells him to do, which is almost
> >certainly something *other* than what a kernel.org kernel should do.
> >If he's running Ubuntu, it should do whatever Ubuntu does.  If he's
> >on Fedora Core, it should poke the RedHat bugzilla, and so on.
> >
> >If he's running a kernel.org kernel, it's probably safe to assume *some*
> >level of clue
> >
> 
> This was actually just an example circunstance of why somebody would
> not report a bug. Dozens of other circunstances may be given, and it
> just illustrates why would be good to have those bug reports without
> user interaction. Of course I can go to bugzilla and fill a report
> upon a bug, but I wouldn't care to have bug reports being sent from my
> servers automatically, if it's an option. This would ensure that even
> bug report from non-caring users are, well, reported.

Well, unless we have some volunteer to go through the bugreports and
sort them/kill the invalid ones/etc... this is going to do more harm
than good.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-07-10 17:32 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-09  8:45 Daniel Bonekeeper
2006-07-09  9:45 ` Michal Piotrowski
2006-07-09 10:29   ` Daniel Bonekeeper
2006-07-09 12:58     ` Adrian Bunk
2006-07-09 18:46       ` Daniel Bonekeeper
2006-07-09 19:11         ` Adrian Bunk
2006-07-09 20:01           ` Daniel Bonekeeper
2006-07-09 20:19             ` Valdis.Kletnieks
2006-07-09 20:27               ` Daniel Bonekeeper
2006-07-10  8:11                 ` Pavel Machek [this message]
2006-07-10 17:40                   ` Daniel Bonekeeper
2006-07-10 17:59                     ` Valdis.Kletnieks
2006-07-10 22:05                       ` Daniel Bonekeeper
2006-07-10 23:41                         ` Lee Revell
2006-07-11  1:15                           ` Daniel Bonekeeper
2006-07-10 18:41                     ` Horst von Brand
2006-07-10 21:34                       ` Daniel Bonekeeper
2006-07-11 14:16                         ` Horst von Brand
2006-07-09 20:24             ` Diego Calleja
2006-07-09 20:37               ` Daniel Bonekeeper
2006-07-09 22:19                 ` Diego Calleja
2006-07-09 22:49                   ` Daniel Bonekeeper
2006-07-09 20:25             ` Jesper Juhl

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=20060710081131.GA2251@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thehazard@gmail.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