From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Bug reports: Making sure you provide all system info
Date: Thu, 29 May 2003 13:09:31 -0400 [thread overview]
Message-ID: <3ED63ECB.9040705@techsource.com> (raw)
Is there a script people can run which will dig all necessary system
informaion out of /proc so that when one wants to report a bug, they
just run the script and dump the output into the lkml email?
I see lots of bug reports which provide very similar kinds of
information. It seems to be so common a thing to do that it should be
automated, no?
next reply other threads:[~2003-05-29 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 17:09 Timothy Miller [this message]
2003-05-29 21:08 ` Bug reports: Making sure you provide all system info Riley Williams
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=3ED63ECB.9040705@techsource.com \
--to=miller@techsource.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