From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Stefan Richter" <stefanr@s5r6.in-berlin.de>
Cc: "Adrian Bunk" <bunk@kernel.org>,
"Arjan van de Ven" <arjan@infradead.org>,
"Bosko Radivojevic" <bosko.radivojevic@gmail.com>,
linux-kernel@vger.kernel.org,
"Natalie Protasevich" <protasnb@gmail.com>
Subject: Re: Number of bugs - statistics
Date: Thu, 22 May 2008 18:38:18 +0200 [thread overview]
Message-ID: <e2e108260805220938w718d39ddh633c48a6373fd682@mail.gmail.com> (raw)
In-Reply-To: <48359DE1.8050600@s5r6.in-berlin.de>
On Thu, May 22, 2008 at 2:28 PM, Bosko Radivojevic
<bosko.radivojevic@gmail.com> wrote:
> Is there any kind of analysis of number of (reported or resolved) bugs
> through time in Linux kernel floating around? I'm trying to convince
> my colleagues that newer kernel version does not mean more bugs than
> the previous 'well tested' ones.
The following summary of a speech by Andrew Morton contains good
arguments as why you should use a recent kernel:
http://lwn.net/Articles/278647/
Bart.
next prev parent reply other threads:[~2008-05-22 16:38 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
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 [this message]
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=e2e108260805220938w718d39ddh633c48a6373fd682@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=arjan@infradead.org \
--cc=bosko.radivojevic@gmail.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=protasnb@gmail.com \
--cc=stefanr@s5r6.in-berlin.de \
/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®