From: "J.A. Magallon" <jamagallon@able.es>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: Mike Black <mblack@csihq.com>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.17
Date: Sun, 23 Dec 2001 00:41:04 +0100 [thread overview]
Message-ID: <20011223004104.G6735@werewolf.able.es> (raw)
In-Reply-To: <Pine.LNX.4.21.0112211439390.7313-100000@freak.distro.conectiva> <002701c18adf$b9f0f140$ac542341@cfl.rr.com> <20011222185940.6a646662.skraw@ithnet.com>
In-Reply-To: <20011222185940.6a646662.skraw@ithnet.com>; from skraw@ithnet.com on Sat, Dec 22, 2001 at 18:59:40 +0100
On 20011222 Stephan von Krawczynski wrote:
>On Sat, 22 Dec 2001 06:56:44 -0500
>"Mike Black" <mblack@csihq.com> wrote:
>
>> My thanks to for Marcelo's efforts...but....
>>
>> Is there any way we can get Marcelo, Rik, and Andrea to work together on the
>> "stable" version now (a Linux tribunal)?
>
>Would you mind to give us a short hint on the implicit "instability" you are
>exactly talking about? I think 2.4.17 is in various ways well worked out and
>maintained. There are further improvements possible for sure, but that is a
>normal thing. Anyway I cannot really see any major instability issues that
>require instant brainstorming. I am confident in Marcelo's maintenance.
>
They are not different branches. Perhaps what is confusing him (and sometimes
also confuses me), is that there are patches in aa kernel (I am not a
compulsive patcher...) that look like basic bug fixes or simple but effective
enhancements that never reach mainline, they are only in aa for ages (looking
at andrea's dir in ftp.kernel.org: all the _vm patches, the spinlock-cacheline,
compiler.h, rwsem, parent-timeslice, etc.). Nothing wrt numa, tux, uml or lvm.
How about a 18-pre1 taking from aa all that is usefull and not really intrusive ?
--
J.A. Magallon # Let the source be with you...
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.17-beo #1 SMP Fri Dec 21 21:39:36 CET 2001 i686
next prev parent reply other threads:[~2001-12-22 23:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 16:45 Linux 2.4.17 Marcelo Tosatti
2001-12-21 19:13 ` Steven Spence
2001-12-21 19:15 ` Steven Spence
2001-12-21 19:47 ` [PATCH] Linux 2.4.17 - compile error in drivers/video/aty/aty_base.c Tobias Ringstrom
2001-12-22 11:56 ` Linux 2.4.17 Mike Black
2001-12-22 17:59 ` Stephan von Krawczynski
2001-12-22 23:41 ` J.A. Magallon [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-21 20:16 Dan Kegel
2001-12-21 19:44 ` Marcelo Tosatti
2001-12-21 21:59 ` Dan Kegel
2001-12-21 22:11 ` Rik van Riel
2001-12-21 23:10 ` Oliver Xymoron
2001-12-22 0:34 ` David Relson
2001-12-22 0:52 ` Mike Castle
2001-12-22 5:19 ` Craig I. Hagan
2001-12-22 8:15 ` Daniel Phillips
2001-12-21 21:09 ` David Gomez
2001-12-22 4:12 ` John Alvord
2001-12-22 18:12 ` David A. Frantz
2001-12-22 23:05 ` Alan Cox
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=20011223004104.G6735@werewolf.able.es \
--to=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mblack@csihq.com \
--cc=skraw@ithnet.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