From: Andi Kleen <ak@suse.de>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Chris Friesen <cfriesen@nortel.com>, Andi Kleen <ak@suse.de>,
Mark Gross <mgross@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: Why is 2.6.12.2 less stable on my laptop than 2.6.10?
Date: Fri, 15 Jul 2005 04:09:14 +0200 [thread overview]
Message-ID: <20050715020914.GQ23737@wotan.suse.de> (raw)
In-Reply-To: <9a8748490507141906fb7e5b@mail.gmail.com>
> You can't test everything this way, nor should you, but you can test
> many things, and adding a bit of formal testing to the release
> procedure wouldn't be a bad thing IMO.
In the linux model that's left to the distributions. In fact doing it properly
takes months. You wouldn't want to wait months for a new mainline kernel.
Formal testing is not really compatible with "release early, release often"
You could do things like "run LTP first", but in practice LTP rarely finds
bugs.
-Andi
next prev parent reply other threads:[~2005-07-15 2:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200507140912.22532.mgross@linux.intel.com.suse.lists.linux.kernel>
2005-07-15 0:38 ` Andi Kleen
2005-07-15 1:45 ` Jesper Juhl
2005-07-15 2:02 ` Chris Friesen
2005-07-15 2:06 ` Jesper Juhl
2005-07-15 2:09 ` Andi Kleen [this message]
2005-07-15 21:33 ` Mark Gross
2005-07-15 2:16 ` Dave Airlie
2005-07-15 21:39 ` Mark Gross
2005-07-15 2:09 ` Dave Jones
2005-07-15 21:47 ` Mark Gross
2005-07-15 22:19 ` Dave Jones
2005-07-15 22:25 ` David Lang
2005-07-15 23:14 ` Rik van Riel
2005-07-18 21:14 ` Mark Gross
2005-07-19 10:12 ` Paolo Ciarrocchi
2005-07-15 2:09 ` Parag Warudkar
2005-07-15 2:14 ` Andi Kleen
2005-07-15 13:32 ` Alan Cox
2005-07-14 16:12 Mark Gross
2005-07-14 23:55 ` Andrew Morton
2005-07-15 8:45 ` Pavel Machek
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=20050715020914.GQ23737@wotan.suse.de \
--to=ak@suse.de \
--cc=cfriesen@nortel.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgross@linux.intel.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®