From: Rik van Riel <riel@redhat.com>
To: Tarkan Erimer <tarkan@netone.net.tr>
Cc: Arjan van de Ven <arjan@infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion About Kernel Releases
Date: Wed, 21 May 2008 15:55:59 -0400 [thread overview]
Message-ID: <20080521155559.11f880d1@bree.surriel.com> (raw)
In-Reply-To: <48342ADC.3030509@netone.net.tr>
On Wed, 21 May 2008 16:59:56 +0300
Tarkan Erimer <tarkan@netone.net.tr> wrote:
> Even, Linus can releases new kernels more quickly. Because, testing
> purpose should be handled by someone else like Chris did for 2.6.x.y.
If Linus were to go straight from merge window to merge window,
with stabilization happening in parallel, then there would be
no stable basis at the start of each merge window and bugs can
just pile up.
Speeding things up could lead to the same kind of code quality
issues we used to have in the 1.3, 2.1, 2.3 and 2.5 kernel series.
Slowing down regularly is good, not bad.
--
All rights reversed.
next prev parent reply other threads:[~2008-05-21 19:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 13:08 Tarkan Erimer
2008-05-21 13:38 ` Arjan van de Ven
2008-05-21 13:48 ` Pekka Enberg
2008-05-21 14:00 ` Tarkan Erimer
2008-05-21 14:32 ` Mike Snitzer
2008-05-21 15:15 ` Tarkan Erimer
2008-05-21 15:26 ` Pekka Enberg
2008-05-24 3:11 ` Enrico Weigelt
2008-05-21 13:59 ` Tarkan Erimer
2008-05-21 14:28 ` Arjan van de Ven
2008-05-21 14:50 ` Tarkan Erimer
2008-05-21 15:12 ` Arjan van de Ven
2008-05-21 17:31 ` Chris Wright
2008-05-22 6:46 ` Tarkan Erimer
2008-05-21 19:55 ` Rik van Riel [this message]
2008-05-21 14:37 ` Oliver Pinter
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=20080521155559.11f880d1@bree.surriel.com \
--to=riel@redhat.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tarkan@netone.net.tr \
/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®