From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Ionut Georgescu <george@physik.tu-cottbus.de>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@conectiva.com.br>
Subject: Re: Linux 2.4 future
Date: Tue, 02 Dec 2003 08:38:03 -0500 [thread overview]
Message-ID: <3FCC95BB.60205@wmich.edu> (raw)
In-Reply-To: <20031202131311.GA10915@physik.tu-cottbus.de>
Ionut Georgescu wrote:
> Because new hardware requires newest kernel, and neither I, nor the
> majority of the users out there have the knowledge to 'forward' apply
> patches.
>
> Even if 2.4 is phasing out, the process has just begun and it will last
> a lot until 2.6 will be ready for production systems.
>
> We are not talking about a fancy, experimental feature. We are talking
> about a mature, serious project, that has been traveling for 3 years
> along the 2.4 kernel and with even more years of testing and research
> behind. I find it just pitty for the linux kernel not to include it.
>
> When going to a conference, you don't present the brand new stuff you
> have just computed or measured the night before, because you just can't
> know if it is correct or not. Instead, you will present older, but
> mature work, that you can swear on. The same with the 2.6 kernel.
> Everybody is pushing it in front, but no one is using it for production
> systems. XFS and 2.4 are, even together, old, mature work, that anybody
> would 'present' anywhere.
>
> Regards,
> Ionut
The point was, the patch is perfectly and easily usable the way it is.
There stands to be no reason to make it part of the vanilla kernel other
than a very slight convenience factor for a small minority of users.
Tosatti thinks that that versus changes to this stable kernel that touch
common code are unacceptable. Despite the maturity of the project, it
just doesn't make sense to include it in the vanilla kernel, it would be
a disservice to the rest of the users of 2.4.x kernels that do so for
stability, not only in the not crashing sense, but also in the code-base
sense. And the number of users who don't use xfs so greatly outnumber
the users that do that it's a mute point for Tosatti.
Just suck it up, plug on with the complex command of cat xfs.patch |
patch -p1 or move up to 2.6. Anyone using xfs can obviously do either
already and everyone not can continue not being affected by new code if
they dont want to.
next prev parent reply other threads:[~2003-12-02 13:38 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 14:25 Linux 2.4 future Marcelo Tosatti
2003-12-01 15:04 ` Ian Kent
2003-12-01 15:33 ` Christoph Hellwig
2003-12-01 21:36 ` Peter C. Norton
2003-12-01 23:54 ` Arjan van de Ven
2003-12-02 1:11 ` Ian Kent
2003-12-02 20:13 ` Peter C. Norton
2003-12-02 20:10 ` Peter C. Norton
2003-12-02 20:18 ` Arjan van de Ven
2003-12-02 20:46 ` Peter C. Norton
2003-12-03 1:23 ` Ian Kent
2003-12-03 10:36 ` Matthias Andree
2003-12-03 14:49 ` Ian Kent
2003-12-03 15:00 ` Matthias Andree
2003-12-04 6:24 ` Ian Kent
2003-12-02 21:56 ` Bryan Whitehead
2003-12-02 8:17 ` Christoph Hellwig
2003-12-02 1:09 ` Ian Kent
2003-12-02 2:23 ` snpe
2003-12-02 6:39 ` Jan-Benedict Glaw
2003-12-02 18:04 ` Linus Torvalds
2003-12-02 18:45 ` Jan-Benedict Glaw
2003-12-02 19:09 ` Linus Torvalds
2003-12-02 19:13 ` Jan-Benedict Glaw
2003-12-02 19:39 ` Gene Heskett
2003-12-02 20:13 ` Jeff Garzik
2003-12-02 20:32 ` Stephan von Krawczynski
2003-12-02 21:48 ` Gene Heskett
2003-12-02 21:56 ` Linus Torvalds
2003-12-03 2:36 ` Harald Arnesen
2003-12-03 9:21 ` Helge Hafting
2003-12-02 19:59 ` snpe
2003-12-02 22:30 ` Mike Fedyk
2003-12-02 22:43 ` Arnaldo Carvalho de Melo
2003-12-03 14:08 ` snpe
2003-12-03 13:26 ` Christoph Hellwig
2003-12-02 8:18 ` Christoph Hellwig
2003-12-01 15:26 ` Norberto Bensa
2003-12-01 23:30 ` 2.6 security patches merged? was: " Mike Fedyk
2003-12-02 0:06 ` Chris Wright
2003-12-02 0:58 ` Måns Rullgård
2003-12-02 1:56 ` Chris Wright
2003-12-02 11:55 ` Marcelo Tosatti
2003-12-02 9:00 ` Matthias Andree
2003-12-02 11:54 ` Ionut Georgescu
2003-12-02 12:03 ` Arnaldo Carvalho de Melo
2003-12-02 13:13 ` Ionut Georgescu
2003-12-02 13:38 ` Ed Sweetman [this message]
2003-12-02 14:12 ` Arnaldo Carvalho de Melo
2003-12-02 16:01 ` Ionut Georgescu
2003-12-02 16:08 ` Jeff Garzik
2003-12-02 18:20 ` John Bradford
2003-12-02 20:19 ` Ville Herva
2003-12-02 21:40 ` Chris Wright
2003-12-02 20:09 ` Stephan von Krawczynski
2003-12-02 20:24 ` Arnaldo Carvalho de Melo
2003-12-02 20:45 ` Stephan von Krawczynski
2003-12-02 21:03 ` Arnaldo Carvalho de Melo
[not found] ` <Pine.LNX.4.58.0312021402360.17892@moje.vabo.cz>
[not found] ` <20031202131512.GU13388@conectiva.com.br>
[not found] ` <Pine.LNX.4.58.0312021433360.8417@moje.vabo.cz>
[not found] ` <20031202135423.GB13388@conectiva.com.br>
2003-12-02 20:21 ` Tomas Konir
2003-12-02 18:53 ` Mike Fedyk
2003-12-02 19:06 ` Valdis.Kletnieks
2003-12-02 23:13 ` Jose Luis Domingo Lopez
2003-12-03 18:22 ` bill davidsen
2003-12-04 1:24 ` jw schultz
2003-12-04 1:47 ` Mike Fedyk
2003-12-04 3:45 ` Tim Connors
2003-12-04 5:41 ` Willy Tarreau
2003-12-05 0:14 ` jw schultz
2003-12-01 15:56 ` Marcelo Tosatti
2003-12-01 21:02 ` David S. Miller
2003-12-03 21:26 ` Jan Rychter
2003-12-03 20:51 ` Jeff Garzik
2003-12-03 21:14 ` Willy Tarreau
2003-12-05 15:33 ` John Jasen
2003-12-05 22:23 ` Mike Fedyk
2003-12-06 15:49 ` Max Valdez
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=3FCC95BB.60205@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=acme@conectiva.com.br \
--cc=george@physik.tu-cottbus.de \
--cc=linux-kernel@vger.kernel.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