From: Wade Hampton <whampton@staffnet.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: oops script for /usr/src/linux/scripts
Date: Mon, 09 Apr 2001 12:03:37 -0400 [thread overview]
Message-ID: <3AD1DD59.C28C401C@staffnet.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
I made a simple bug_report.sh script to facilitate
generating a bug report. It could be included in
/usr/src/linux/scripts and could be referenced in
/usr/src/linux/BUG-REPORTING.
If anyone is interested, please see attached.
Cheers,
--
W. Wade, Hampton <whampton@staffnet.com>
[-- Attachment #2: bug_report.sh --]
[-- Type: application/x-sh, Size: 2391 bytes --]
reply other threads:[~2001-04-09 16:03 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=3AD1DD59.C28C401C@staffnet.com \
--to=whampton@staffnet.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox