mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Parag Warudkar" <parag.warudkar@gmail.com>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: "Daniel Hazelton" <dhazelton@enter.net>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: How to reduce the number of open kernel bugs
Date: Fri, 2 May 2008 14:25:47 -0400	[thread overview]
Message-ID: <82e4877d0805021125y1e11deb4qaa57ac493cf41aba@mail.gmail.com> (raw)
In-Reply-To: <20080502180151.GD5838@cs181133002.pp.htv.fi>

On Fri, May 2, 2008 at 2:01 PM, Adrian Bunk <bunk@kernel.org> wrote:
> On Fri, May 02, 2008 at 01:30:23PM -0400, Parag Warudkar wrote:
>  > 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!
>
>  And the point is?
>

Point being that no one can force anyone to do anything in the setting
in which kernel developers work.
Distros have been doing this since ever and people have no choice but
to move on.
(Everybody works out of their own (or employer's) interest and
judgement - so telling some one to act otherwise will not be a whole
lot productive.)

>
>  You completely miss the point.

I am not - my point is that you can't do  much about it that will go
long way in resolving the issue.

>  And in any case, being more friendly to a bug submitter.

Well again -  you can't force people to do something like that. In
your example it would amount to the maintainer going against his/her
own judgement - however wrong it is to you and me, to the person who
can actually fix it - it's not a possibility. So you have to just
accept it and reassign it to some one else who is interested/capable -
for that I suggested tracking such bugs under a new STATUS.

Parag

  reply	other threads:[~2008-05-02 18:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 14:42 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
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 [this message]
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=82e4877d0805021125y1e11deb4qaa57ac493cf41aba@mail.gmail.com \
    --to=parag.warudkar@gmail.com \
    --cc=bunk@kernel.org \
    --cc=dhazelton@enter.net \
    --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 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®