All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Matthias Juchem <juchem@uni-mannheim.de>,
	"Jeremy M. Dolan" <jmd@foozle.turbogeek.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Bug reporting script? (was: removal of redundant line in documentation)
Date: Tue, 9 Jan 2001 00:45:55 +0100	[thread overview]
Message-ID: <20010109004555.A7021@bug.ucw.cz> (raw)
In-Reply-To: <20010106075402.A3377@foozle.turbogeek.org> <Pine.LNX.4.30.0101061327090.4099-100000@gandalf.math.uni-mannheim.de>
In-Reply-To: <Pine.LNX.4.30.0101061327090.4099-100000@gandalf.math.uni-mannheim.de>; from Matthias Juchem on Sat, Jan 06, 2001 at 01:33:16PM +0100

Hi!

> > If ver_linux can take off one of those steps, why not include a script
> > which takes care of ALL the leg work? All of the files it asks the
> > reporter to include are o+r...
> 
> If have started a script that produces the following output. ( some fields
> need to be filled, but the structure will be like that). If you have additional
> ideas, please tell me. I'll include some more version numbers from system tools
> and, maybe, a routine that calls ksymoops.

This is horrible bugreport. Kill "keywords". Putting "modules" into
keywords i not going to help anyone. Having "4. Kernel version" and
minuses before actuall version is not helpfull, either.

								Pavel

> 4. Kernel version
> ----------------------------------------------
> Linux version 2.4.0 (root@gandalf) (gcc version 2.95.2 19991024 (release)) #6 Sat Jan 6 03:37:57 CET 2001

-- 
I'm pavel@ucw.cz. "In my country we have almost anarchy and I don't care."
Panos Katsaloulis describing me w.r.t. patents at discuss@linmodems.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-09 16:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06  5:51 [PATCHlet]: removal of redundant line in documentation Matthias Juchem
2001-01-06 13:54 ` Bug reporting script? (was: removal of redundant line in documentation) Jeremy M. Dolan
2001-01-06 12:33   ` Matthias Juchem
2001-01-08 23:45     ` Pavel Machek [this message]
2001-01-10 19:05       ` Matthias Juchem
2001-01-11  8:58         ` Pavel Machek
2001-01-06 17:40   ` Augusto César Radtke
2001-01-06 22:19     ` db
2001-01-07  1:21     ` Bug reporting script? Matthias Juchem

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=20010109004555.A7021@bug.ucw.cz \
    --to=pavel@suse.cz \
    --cc=jmd@foozle.turbogeek.org \
    --cc=juchem@uni-mannheim.de \
    --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.