Date: Wed, 3 Sep 2003 11:49:19 +0200
From: Roger Luethi <rl@hellgate.ch>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Damian Kolkowski <deimos@deimos.one.pl>,
       Danny ter Haar <dth@ncc1701.cistron.net>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4(-mmX) via-rhine ethernet onboard C3 mini-itx doesn't work
Message-ID: <20030903094919.GB28594@k3.hellgate.ch>
Mail-Followup-To: Mikael Pettersson <mikpe@csd.uu.se>,
	Damian Kolkowski <deimos@deimos.one.pl>,
	Danny ter Haar <dth@ncc1701.cistron.net>,
	linux-kernel@vger.kernel.org
References: <bj447c$el6$1@news.cistron.nl> <20030903074902.GA1786@deimos.one.pl> <16213.46254.376174.466098@gargle.gargle.HOWL>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16213.46254.376174.466098@gargle.gargle.HOWL>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1026
Lines: 19

On Wed, 03 Sep 2003 11:30:22 +0200, Mikael Pettersson wrote:
> I saw your previous report. It was basically information-free and impossible
> to base any problem analysis on. If you want your bug reports to have a
> chance of being acted upon, follow the documented bug reporting procedure.

Most users are more than happy to provide additional information when asked
for it. In my personal experience, the documented bug reporting procdure is
a time consuming way of producing lots of information, most of which is
irrelevant to the case in question, and which is usually lacking the
information _I_ am looking for. For me, it tends to be less work to ask the
user for the specific details than to sift through a lengthy standard bug
report looking for it. YMMV, of course.

Roger
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/