mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Subject: Re: [RFC][PATCH] Update REPORTING-BUGS
Date: Tue, 27 Nov 2007 00:30:53 +0100	[thread overview]
Message-ID: <20071126233052.GF917@stusta.de> (raw)
In-Reply-To: <200711262344.25223.rjw@sisk.pl>

On Mon, Nov 26, 2007 at 11:44:24PM +0100, Rafael J. Wysocki wrote:
> On Monday, 26 of November 2007, Adrian Bunk wrote:
> > On Mon, Nov 26, 2007 at 01:51:37AM +0100, Rafael J. Wysocki wrote:
> > > On Monday, 26 of November 2007, Adrian Bunk wrote:
>...
> > > > We will never get 100% of all bugs fixed.
> > > > 
> > > > Let's get back to the fact that we have many bug reports that could be 
> > > > fixed within a reasonable amount of time but are not.
> > > 
> > > Do you have specific examples?
> > 
> > Take e.g. #3938
> 
> Are you sure that this one hasn't been fixed?  The reporter doesn't seem to be
> responsive ...
> 
> > or #4039
> 
> Same here.

Saying "reporter doesn't seem to be responsive" is a joke if there was
zero activity in solving any of these bugs for nearly three years.

They might (or might not) be fixed by chance now, but they should have
been fixed in the beginning of 2005 as a result of the bug reports.

You can now claim these are too old, but you'll find for any bug age 
bugs that both should be solvable for a developer knowing the kernel 
code in question and that have not been seriously debugged.

> > as examples.  
> 
> Greetings,
> Rafael

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-11-26 23:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-25 20:57 Rafael J. Wysocki
2007-11-25 21:12 ` Adrian Bunk
2007-11-25 21:51   ` Rafael J. Wysocki
2007-11-25 21:51     ` Adrian Bunk
2007-11-25 23:00       ` Rafael J. Wysocki
2007-11-25 23:13         ` Adrian Bunk
2007-11-26  0:04           ` Rafael J. Wysocki
2007-11-26  0:06             ` Adrian Bunk
2007-11-26  0:51               ` Rafael J. Wysocki
2007-11-26 21:20                 ` Adrian Bunk
2007-11-26 22:44                   ` Rafael J. Wysocki
2007-11-26 23:30                     ` Adrian Bunk [this message]
2007-11-27  0:21                       ` Rafael J. Wysocki
2007-11-26 21:02 ` [RFC][PATCH] Update REPORTING-BUGS (rev. 2) Rafael J. Wysocki
2007-11-27  8:50   ` Jarek Poplawski
2007-11-27  8:54     ` Jarek Poplawski

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=20071126233052.GF917@stusta.de \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bzolnier@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®