From: Vojtech Pavlik <vojtech@suse.cz>
To: "Michał Piotrowski" <piotrowskim@trex.wsi.edu.pl>
Cc: linux-kernel@vger.kernel.org,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Paul TT <paultt@bilug.linux.it>,
randy_dunlap <rdunlap@xenotime.net>,
Jesper Juhl <jesper.juhl@gmail.com>,
cp@absolutedigital.net
Subject: Re: [ANNOUNCE] ORT - Oops Reporting Tool v.b4
Date: Sun, 3 Jul 2005 22:29:56 +0200 [thread overview]
Message-ID: <20050703202956.GA3534@ucw.cz> (raw)
In-Reply-To: <42C7FBD3.1020002@trex.wsi.edu.pl>
On Sun, Jul 03, 2005 at 04:53:07PM +0200, Michał Piotrowski wrote:
> Here is our (see copyright section ;)) simple script that help to create
> a bug report:
> http://stud.wsi.edu.pl/~piotrowskim/files/ort/beta/ort-b4.tar.bz2
>
> Why do we do this?
> Because many people don't have time to prepare a good (with all
> importrant pieces of information) bug report.
>
> How does it work?
> It creates file with information about your system (software, hardware,
> used modules etc.), add file with oops into it and in the future sends
> it to the chosen mainterner or lkml.
Sorry to say that, but:
I definitely won't be interested in bug reports from an automated tool
like this. I don't have the time to go through the heaps of information
it collects - I need a short and to the point description of the problem
from the user. Most of the time less is more, and if something is
missing, asking is always an option.
As if bug reports filled exactly in accordance with the "Reporting Bugs"
howto from Richard Gooch weren't bad enough.
> How can you help?
> If you know something about bash scripting you can review it, add some
> useful features and make some optimalisations. Or just send me an idea.
>
> Changelog:
> - Cal Peake (greate thanks for big patch ;)){
> - remove the need to run the (whole) script as root
> - add support for Pine MUA
> - add support for nail MUA
> - add pager selection
> - whitespace cleanup
> - user interface consistency
> - code simplification
> - some other small things
> }
>
> Todo before final version:
> - more e-mail clients?
> - nice ascii logo?
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2005-07-03 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 14:53 [ANNOUNCE] ORT - Oops Reporting Tool v.b4 Michał Piotrowski
2005-07-03 15:08 ` Jon Smirl
2005-07-03 15:29 ` Michał Piotrowski
2005-07-03 20:29 ` Vojtech Pavlik [this message]
2005-07-03 21:32 ` Michał Piotrowski
2005-07-04 10:08 ` Tomasz Kłoczko
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=20050703202956.GA3534@ucw.cz \
--to=vojtech@suse.cz \
--cc=cp@absolutedigital.net \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paolo.ciarrocchi@gmail.com \
--cc=paultt@bilug.linux.it \
--cc=piotrowskim@trex.wsi.edu.pl \
--cc=rdunlap@xenotime.net \
/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