mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "SL Baur" <steve@xemacs.org>
To: "Adrian Bunk" <bunk@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to reduce the number of open kernel bugs
Date: Sat, 3 May 2008 03:13:21 -0700	[thread overview]
Message-ID: <ed10ee420805030313r457d8cdfjdbcb346ae928c125@mail.gmail.com> (raw)
In-Reply-To: <20080502124210.GB5838@cs181133002.pp.htv.fi>

On 5/2/08, Adrian Bunk <bunk@kernel.org> wrote:
> Just seen in the kernel Bugzilla (driver anonymized to foobar):

 ... An all too common sequence

This is the kind of stuff that naturally happens when you tie performance
to the progression of bug reports through bug tracking systems.  It's
human nature.

It's not good, but it's human nature.  This situation is *not* unique to Linux.

-sb (My day job is the care and feeding of a Fortune 50 company's internal bug
tracking system)

  reply	other threads:[~2008-05-03 10:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 12:42 Adrian Bunk
2008-05-03 10:13 ` SL Baur [this message]
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
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
2008-05-02 23:15       ` Daniel Hazelton

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=ed10ee420805030313r457d8cdfjdbcb346ae928c125@mail.gmail.com \
    --to=steve@xemacs.org \
    --cc=bunk@kernel.org \
    --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®