[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200804140041.34843.rjw@sisk.pl>
Date: Mon, 14 Apr 2008 00:41:33 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: sclark46@...thlink.net
Cc: Evgeniy Polyakov <johnpol@....mipt.ru>,
Andrew Morton <akpm@...ux-foundation.org>,
Willy Tarreau <w@....eu>, Tilman Schmidt <tilman@...p.cc>,
Valdis.Kletnieks@...edu, Mark Lord <lkml@....ca>,
David Miller <davem@...emloft.net>, jesper.juhl@...il.com,
yoshfuji@...ux-ipv6.org, jeff@...zik.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Reporting bugs and bisection
On Monday, 14 of April 2008, Stephen Clark wrote:
> Evgeniy Polyakov wrote:
> > On Sun, Apr 13, 2008 at 10:33:49PM +0200, Rafael J. Wysocki (rjw@...k.pl) wrote:
> >> Things like this are very disappointing and have a very negative impact on bug
> >> reporters. We should do our best to avoid them.
> >
> > Shit happens. This is a matter of either bug report or those who were in
> > the copy list. There are different people and different situations, in
> > which they do not reply.
> >
> Well less shit would happen if developers would take the time to at least test
> their patches before they were submitted. It like we will just have the poor
> user do our testing for us. What kind of testing do developers do. I been a
> linux user and have followed the LKML for a number of years and have yet to see
> any test plans for any submitted patches.
The (apparent) lack of test plans doesn't imply the patches not being tested,
actually.
My experience indicates that they are tested in the majority of cases. Still,
sometimes they are not and that's when the most damage is done.
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists