From: Ruben Puettmann <ruben@puettmann.net>
To: linux-kernel@vger.kernel.org
Cc: Marc-Christian Petersen <m.c.p@wolk-project.de>
Subject: linux-2.2 future?
Date: Fri, 22 Aug 2003 13:22:25 +0200 [thread overview]
Message-ID: <E19q9zt-0002Cz-00@baloney.puettmann.net> (raw)
In-Reply-To: <mV1t.7Wj.15@gated-at.bofh.it>
> On Wednesday 20 August 2003 13:59, Marc-Christian Petersen wrote:
>
> Hi Alan,
>
>> On Wednesday 20 August 2003 13:46, Alan Cox wrote:
>> he 2.2 tree needs a new maintainer, someone who can spend their entire
>> life refusing patches, being ignored by the mainstream (because 2.2 is
>> boring) and by vendors (who don't ship 2.2 any more).
>
> I want to take 2.2.
>
What's up with linux-2.2 now? Who will do Alan's job in the next year?
Marc is intrested doing this job. I know Marc from linux-2.2.x-secure
and from the wolk project, see http://wolk.sourceforge.net. Why not
Marc? He can surely differentiate between mainstream and a private kernel fork
tree. Or do you think, Marc will merge every single bit out of his kernel tree
into mainstream? I bet he won't
I can't see postings from other people who want to take 2.2.
I think 2.2 is not dead. I often see 2.2 kernels running on systems like
wlan access points or dsl routers from different vendors. 2.2 is often
used where stability is a must-have. At least security fixes have to go in.
What do you think?
Ruben
--
Ruben Puettmann
ruben@puettmann.net
http://www.puettmann.net
next parent reply other threads:[~2003-08-22 12:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mzDG.3ry.27@gated-at.bofh.it>
[not found] ` <mzWX.3MH.5@gated-at.bofh.it>
[not found] ` <mV1t.7Wj.15@gated-at.bofh.it>
2003-08-22 11:22 ` Ruben Puettmann [this message]
2003-08-22 17:46 ` linux-2.2 future? Mike Fedyk
2003-08-22 21:27 A.D.F.
2003-08-25 16:42 ` Marc-Christian Petersen
2003-08-26 15:03 ` Alan Cox
2003-08-27 22:27 ` Neale Banks
2003-08-27 22:40 ` Marc-Christian Petersen
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=E19q9zt-0002Cz-00@baloney.puettmann.net \
--to=ruben@puettmann.net \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
/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;
as well as URLs for NNTP newsgroup(s).