All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bug tracking
Date: Wed, 18 Jan 2006 00:11:53 +0100	[thread overview]
Message-ID: <20060117231153.GG19398@stusta.de> (raw)
In-Reply-To: <20060117150612.345571ef.akpm@osdl.org>

On Tue, Jan 17, 2006 at 03:06:12PM -0800, Andrew Morton wrote:
>...
> c) Privately email the reporter, saying "if this bug is still present in
>    2.6.15, please raise a report at bugzilla.kernel.org"
> 
> I've sent 100-200 of these emails in the past few days.  Of the people
> who've responded, the great majority of these bugs were actually fixed, which
> is nice.
>...

Private emails have the disadvantage that noone else sees them.

Does this imply that it can be assumed that you are tracking all 
unresolved bug reports sent to linux-kernel until they are either 
resolved or in Bugzilla?

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:[~2006-01-17 23:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <OFA777C944.9337E52B-ONC12570C1.0039A0E1-C12570C9.004D661A@avm.de>
2006-01-17 22:44 ` Oops in megaraid , kernel 2.6.14, 2.6.15 on x86_64 Adrian Bunk
2006-01-17 23:06   ` bug tracking Andrew Morton
2006-01-17 23:11     ` Adrian Bunk [this message]
2006-01-17 23:50       ` Andrew Morton
2006-01-18  8:07         ` Adrian Bunk
2021-03-24 22:14 Bug tracking Simon Glass
2021-03-25  7:50 ` Heinrich Schuchardt
2021-03-25  8:14 ` Jagan Teki
2021-03-25 19:38 ` Pratyush Yadav
2021-03-29  8:07   ` Wolfgang Denk

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=20060117231153.GG19398@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.