From: Craig Milo Rogers <rogers@ISI.EDU>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Jan Engelhardt <jengelh@medozas.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Stoyan Gaydarov <stoyboyker@gmail.com>,
linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
gorcunov@gmail.com, akpm@linux-foundation.org, mingo@elte.hu
Subject: Re: From 2.4 to 2.6 to 2.7?
Date: Sat, 19 Jul 2008 13:49:33 -0700 [thread overview]
Message-ID: <20080719204933.GE18350@isi.edu> (raw)
In-Reply-To: <4881AB31.7010400@keyaccess.nl>
On 08.07.19, Rene Herman wrote:
> Really, find me a single Linux developer who wouldn't try just a little bit
> harder for a big 3.0 release. This is still a community, not yet a boring
> office schedule...
I'm afraid that the allure of 3.0 would mean that everyone
would want to get their shiny new subsystem/scheduler
rewrite/bootstrap file format change/whatever incorporated into it,
resulting in a protracted integration period and an unstable system.
According to this line of thought, Linus should simply announce
version 3.0 with no forewarning...
Craig Milo Rogers
next prev parent reply other threads:[~2008-07-19 20:50 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 2:10 From 2.4 to 2.6 to 2.7? Stoyan Gaydarov
2008-07-15 2:22 ` Linus Torvalds
2008-07-15 2:31 ` Stoyan Gaydarov
2008-07-15 2:47 ` Linus Torvalds
2008-07-15 3:55 ` david
2008-07-15 5:31 ` Willy Tarreau
2008-07-15 6:40 ` Rafael C. de Almeida
2008-07-15 7:23 ` Stoyan Gaydarov
2008-07-15 7:49 ` Jan Engelhardt
2008-07-17 17:25 ` Jan Engelhardt
2008-07-17 19:56 ` Craig Milo Rogers
2008-07-17 20:21 ` Jan Engelhardt
2008-07-19 8:00 ` Craig Milo Rogers
2008-07-19 8:52 ` Rene Herman
2008-07-19 20:49 ` Craig Milo Rogers [this message]
2008-07-19 20:56 ` david
2008-07-19 21:56 ` Jan Engelhardt
2008-07-20 8:34 ` Rene Herman
2008-07-20 14:53 ` Stefanos Harhalakis
2008-07-19 19:30 ` Peter T. Breuer
2008-07-19 21:16 ` Craig Milo Rogers
2008-07-19 23:10 ` Peter T. Breuer
2008-07-15 8:29 ` Bernd Petrovitsch
2008-07-15 12:41 ` Kasper Sandberg
2008-07-15 13:18 ` Alberto Gonzalez
2008-07-15 18:06 ` Charles grey wolf Banas
2008-07-15 20:43 ` Adrian Bunk
2008-07-16 7:53 ` Jan Engelhardt
2008-07-16 7:57 ` Rene Herman
2008-07-17 22:16 ` Adrian Bunk
2008-07-15 10:10 ` Andi Kleen
2008-07-15 11:31 ` Jan Engelhardt
2008-07-15 15:20 ` Linus Torvalds
2008-07-15 15:27 ` Parag Warudkar
2008-07-15 15:32 ` Alan Cox
2008-07-18 9:02 ` Andi Kleen
2008-07-16 21:11 ` Lennart Sorensen
2008-07-15 12:38 ` Alan Cox
2008-07-15 14:07 ` Byron Stanoszek
2008-07-16 21:14 ` Lennart Sorensen
2008-07-17 0:03 ` Alex Chiang
2008-07-17 12:38 ` Lennart Sorensen
2008-07-17 20:02 ` Alex Chiang
2008-07-15 14:24 ` Cyrill Gorcunov
2008-07-15 16:36 ` Tobias Brox
2008-07-15 18:04 ` H. Peter Anvin
2008-07-16 4:22 ` Rene Herman
2008-07-16 6:55 ` Rafael C. de Almeida
2008-07-16 7:17 ` Rene Herman
2008-07-16 7:30 ` Rene Herman
2008-07-16 9:34 ` Peter T. Breuer
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 22:05 Alastair Stevens
2008-07-17 22:40 ` Lennart Sorensen
2008-07-18 8:23 ` Peter T. Breuer
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=20080719204933.GE18350@isi.edu \
--to=rogers@isi.edu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gorcunov@gmail.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rene.herman@keyaccess.nl \
--cc=stoyboyker@gmail.com \
--cc=torvalds@linux-foundation.org \
/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