From: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>
To: linux <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>
Subject: Script to help users to report a BUG
Date: Sun, 19 Jun 2005 22:32:16 +0200 [thread overview]
Message-ID: <4d8e3fd30506191332264eb4ae@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi all,
what do you think about this simple idea of a script that could help
users to fill better BUG reports ?
The usage is quite simple, put the attached file in
/usr/src/linux/scripts and then:
[root@frodo scripts]# ./report-bug.sh /tmp/BUGREPORT/
cat: /proc/scsi/scsi: No such file or directory
[root@frodo scripts]# ls /tmp/BUGREPORT/
cpuinfo.bug ioports.bug modules.bug software.bug
iomem.bug lspci.bug scsi.bug version.bug
Now you can simply attach all the .bug files to the bugzilla report or
inline them in a email.
The script is rude but it is enough to give you an idea of what I have in mind.
Any comment ?
--
Paolo
[-- Attachment #2: report-bug.sh --]
[-- Type: application/x-sh, Size: 510 bytes --]
next reply other threads:[~2005-06-19 20:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 20:32 Paolo Ciarrocchi [this message]
2005-06-22 19:08 ` Script to help users to report a BUG randy_dunlap
2005-06-22 20:52 ` Michał Piotrowski
2005-06-23 0:47 ` randy_dunlap
2005-06-23 18:24 ` Jesper Juhl
2005-06-23 19:06 ` randy_dunlap
2005-06-23 19:13 ` Jesper Juhl
2005-06-23 17:48 ` Michał Piotrowski
[not found] ` <4d8e3fd305062313032c9789e8@mail.gmail.com>
2005-06-23 18:23 ` Michał Piotrowski
[not found] ` <4d8e3fd305062400524f0ad358@mail.gmail.com>
2005-06-24 6:52 ` Michał Piotrowski
2005-06-24 15:41 ` randy_dunlap
2005-06-24 8:17 ` Michał Piotrowski
[not found] ` <4d8e3fd3050624032264081edf@mail.gmail.com>
[not found] ` <4d8e3fd3050624050955aac41b@mail.gmail.com>
2005-06-24 14:50 ` Martin J. Bligh
[not found] ` <42B5C747.5050207@trex.wsi.edu.pl>
[not found] ` <4d8e3fd30506200027686cbafa@mail.gmail.com>
[not found] ` <42B6D74B.3020409@trex.wsi.edu.pl>
[not found] ` <4d8e3fd30506201322242d540a@mail.gmail.com>
[not found] ` <4d8e3fd305062205371b0a506d@mail.gmail.com>
[not found] ` <42B951B4.80703@trex.wsi.edu.pl>
[not found] ` <4d8e3fd30506220656241e1521@mail.gmail.com>
[not found] ` <42B9544E.7030007@trex.wsi.edu.pl>
[not found] ` <4d8e3fd305062212343d9849ee@mail.gmail.com>
2005-06-22 21:27 ` Michał Piotrowski
[not found] ` <42B9D391.4020602@trex.wsi.edu.pl>
[not found] ` <4d8e3fd305062300541eca2c10@mail.gmail.com>
2005-06-23 12:06 ` Michał Piotrowski
[not found] ` <9a8748490506231011128f7a38@mail.gmail.com>
2005-06-23 16:21 ` Michał Piotrowski
2005-06-23 18:59 ` Jesper Juhl
2005-06-23 17:27 ` randy_dunlap
2005-06-23 18:28 ` Vara Prasad
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=4d8e3fd30506191332264eb4ae@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=akpm@osdl.org \
--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.