From: Arjan van de Ven <arjan@infradead.org>
To: Tarkan Erimer <tarkan@netone.net.tr>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Suggestion About Kernel Releases
Date: Wed, 21 May 2008 07:28:13 -0700 [thread overview]
Message-ID: <20080521072813.69ae2b0e@infradead.org> (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:
> Arjan van de Ven wrote:
> > what would you want to accomplish with your idea?
> >
>
> To make kernel releases more stable/tested via "testX" series, as
> recently discussed by David Miller's "Slow DOWN, please!!!" thread.
> These "testX" releases will give more opportunity and time to test
> more these new releases. Also, with the aim of the "testX" series,
> the new kernel release schedules/merge windows will be not slow down.
> 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.
sorry but you're wrong ;(
calling something -test won't change anything. It just means it'll get
tested less, not more.
Also the "Slow DOWN please" had NOTHING to do with releases, but only
with what happens during the actual merge window.
next prev parent reply other threads:[~2008-05-21 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 13:08 Suggestion About Kernel Releases 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 [this message]
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
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=20080521072813.69ae2b0e@infradead.org \
--to=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 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.