public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michał Piotrowski" <piotrowskim@trex.wsi.edu.pl>
To: linux-kernel@vger.kernel.org,
	Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
	Paul TT <paultt@bilug.linux.it>,
	randy_dunlap <rdunlap@xenotime.net>,
	Vojtech Pavlik <vojtech@suse.cz>,
	Jesper Juhl <jesper.juhl@gmail.com>,
	cp@absolutedigital.net
Subject: [ANNOUNCE] OOPS Reporting Tool v.b5
Date: Mon, 04 Jul 2005 14:44:18 +0200	[thread overview]
Message-ID: <42C92F22.80708@trex.wsi.edu.pl> (raw)

Hi all,

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-b5.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.

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:
now you may do:
- short report (first 5 points)
- long report (old verbose style)
- custom report (you can choose what do you want to send)
- from template (ie. with USB informations)

- new logo (Maciej Soltysiak)

Todo:
- more e-mail clients
- more templates

Regards,
Michał Piotrowski

                 reply	other threads:[~2005-07-04 12:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42C92F22.80708@trex.wsi.edu.pl \
    --to=piotrowskim@trex.wsi.edu.pl \
    --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=rdunlap@xenotime.net \
    --cc=vojtech@suse.cz \
    /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