mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Natalie Protasevich <protasnb@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	Bosko Radivojevic <bosko.radivojevic@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Number of bugs - statistics
Date: Thu, 22 May 2008 20:33:18 +0300	[thread overview]
Message-ID: <20080522173318.GD2727@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <32209efe0805221008m1850730cxdb26d9bdeb9c43fc@mail.gmail.com>

On Thu, May 22, 2008 at 10:08:49AM -0700, Natalie Protasevich wrote:
> On Thu, May 22, 2008 at 9:50 AM, Adrian Bunk <bunk@kernel.org> wrote:
>...
> >> by various criteria: ALSA bugs
> >> are numerous, which is not important for most enterprise server users
> >> who would completely disregard this category, whereas desktop users
> >> will probably concentrate on those more than any other.
> >
> > The majority of machines running Linux most likely runs with ARM CPUs.
> >
> > Show me any public source you want to use for getting serious data for
> > this area.
> 
> There is no one, except dispersed reports and ... appropriate
> implementation involving search engine comes to mind.

Much of this information will never be published at any place where 
Google could find it.

> >> So the answer
> >> to question about kernel stability would be more adequate depending on
> >> who's asking.
> >
> > You must not confuse "number of reported bugs" with "kernel stability" -
> > these two can be quite decoupled.
> 
> Number of existing, proven and prioritized  bugs maybe better to say.
> I think there is a correlation.

Some correlaton.

If people are aware of the weaknesses and the many obvious ways to 
manipulate such statistics.

> --Natalie

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:[~2008-05-22 17:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 12:28 Bosko Radivojevic
2008-05-22 14:41 ` Adrian Bunk
2008-05-22 14:51   ` Arjan van de Ven
2008-05-22 15:47     ` Natalie Protasevich
2008-05-22 15:54     ` Adrian Bunk
2008-05-22 16:20       ` Natalie Protasevich
2008-05-22 16:50         ` Adrian Bunk
2008-05-22 17:08           ` Natalie Protasevich
2008-05-22 17:33             ` Adrian Bunk [this message]
2008-05-22 17:51               ` Natalie Protasevich
2008-05-22 18:11                 ` Adrian Bunk
2008-05-22 22:18           ` Arjan van de Ven
2008-05-23  9:09             ` Adrian Bunk
2008-05-23 14:11               ` Arjan van de Ven
2008-05-23 16:50                 ` Adrian Bunk
2008-05-23 18:29                   ` Arjan van de Ven
2008-05-23 20:31                     ` Adrian Bunk
2008-05-26 17:05                       ` Dave Jones
2008-05-23 10:35           ` James Courtier-Dutton
2008-05-23 15:35             ` Takashi Iwai
2008-05-22 16:22       ` Stefan Richter
2008-05-22 16:38         ` Bart Van Assche
2008-05-22 17:09         ` Adrian Bunk
2008-05-22 17:45           ` Stefan Richter
2008-05-22 19:17             ` 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=20080522173318.GD2727@cs181133002.pp.htv.fi \
    --to=bunk@kernel.org \
    --cc=arjan@infradead.org \
    --cc=bosko.radivojevic@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=protasnb@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

all inboxes | Powered by JetHome®