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, Jesper Juhl <jesper.juhl@gmail.com>,
	Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
	randy_dunlap <rdunlap@xenotime.net>
Subject: [ANNOUNCE] ORT - Oops Reporting Tool
Date: Fri, 24 Jun 2005 12:50:59 +0200	[thread overview]
Message-ID: <42BBE593.9090407@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-b1.tar.bz2
<http://stud.wsi.edu.pl/%7Epiotrowskim/files/ort/ort-a5.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.

Regards,
Michał Piotrowski


             reply	other threads:[~2005-06-24 12:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-24 10:50 Michał Piotrowski [this message]
2005-06-24 13:42 ` [ANNOUNCE] ORT - Oops Reporting Tool Christian
2005-06-24 15:45   ` randy_dunlap
     [not found]   ` <4d8e3fd3050624085929581341@mail.gmail.com>
2005-06-25 22:00     ` Christian Kujau
2005-06-25 20:19       ` Michał Piotrowski
2005-06-26 18:58       ` Paolo Ciarrocchi
2005-06-25 14:33 ` Michał Piotrowski

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=42BBE593.9090407@trex.wsi.edu.pl \
    --to=piotrowskim@trex.wsi.edu.pl \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.ciarrocchi@gmail.com \
    --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