public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Hazelton <dhazelton@enter.net>
To: "Parag Warudkar" <parag.warudkar@gmail.com>
Cc: "Adrian Bunk" <bunk@kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs
Date: Fri, 2 May 2008 13:44:59 -0400	[thread overview]
Message-ID: <200805021344.59492.dhazelton@enter.net> (raw)
In-Reply-To: <82e4877d0805021030s793835a1le0032673b0f4c6c7@mail.gmail.com>

On Friday 02 May 2008 13:30:23 Parag Warudkar wrote:
> On Fri, May 2, 2008 at 12:29 PM, Daniel Hazelton <dhazelton@enter.net>
> wrote: This is what Adrian was pointing
>
> > ... out and is exactly what shouldn't be happening.
>
> I wasn't arguing that it is what should be happening - I was just
> pointing out that there are worse things than that routinely happen in
> distro bugzillas!

I have to admit that this is the truth. I've seen it myself. (Hell, I won't 
touch a bug-tracking system for that reason.)

> Also I feel that if maintainer refuse to fix something - that's a dead
> end as far as that particular bug is considered. We can try and track
> such bugs in different STATUS but there would have to be people
> interested in digging through such bugs and willing to fix it after
> the maintainer has given up. Which is possible but not likely.
>
> Parag

And I have to agree here. But there should be something that can be done 
to "coax" the maintainers that pull that kind of immature crap into acting 
mature and responsible.

DRH

-- 
Dialup is like pissing through a pipette. Slow and excruciatingly painful.

  reply	other threads:[~2008-05-02 17:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 14:42 How to reduce the number of open kernel bugs Parag Warudkar
2008-05-02 15:11 ` Adrian Bunk
2008-05-02 16:29 ` Daniel Hazelton
2008-05-02 17:27   ` Andi Kleen
2008-05-02 17:40     ` Daniel Hazelton
2008-05-02 17:30   ` Parag Warudkar
2008-05-02 17:44     ` Daniel Hazelton [this message]
2008-05-02 17:48       ` Rafael J. Wysocki
2008-05-02 18:18         ` Andi Kleen
2008-05-02 23:10           ` Daniel Hazelton
2008-05-02 18:01     ` Adrian Bunk
2008-05-02 18:25       ` Parag Warudkar
2008-05-02 23:15       ` Daniel Hazelton
  -- strict thread matches above, loose matches on Subject: below --
2008-05-02 12:42 Adrian Bunk
2008-05-03 10:13 ` SL Baur
2008-05-03 11:21   ` Adrian Bunk
2008-05-03 12:00     ` SL Baur
2008-05-03 15:43     ` Stefan Richter
2008-05-03 15:48       ` Stefan Richter
2008-05-05 18:12       ` Adrian Bunk

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=200805021344.59492.dhazelton@enter.net \
    --to=dhazelton@enter.net \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=parag.warudkar@gmail.com \
    /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