From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: adefacc@tin.it,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Ruben Püttmann" <ruben@puettmann.net>,
"Ville Herva" <vherva@niksula.hut.fi>
Subject: Re: linux-2.2 future?
Date: Thu, 28 Aug 2003 00:40:33 +0200 [thread overview]
Message-ID: <200308280034.19050.m.c.p@wolk-project.de> (raw)
In-Reply-To: <1061910188.20846.39.camel@dhcp23.swansea.linux.org.uk>
On Tuesday 26 August 2003 17:03, Alan Cox wrote:
Hi Alan,
> The problem is that change breaks stuff. a lot of the 2.2 users will
> happily trade lack of LBA48 support for stability and predictability.
> Thats why I took a basically "if its not a serious bugfix its not going
> in" approach
Yeah, I agree with you. Anyway, I've never said I will integrate that IDE
stuff when I become the 2.2 maintainer :) ... I just said I'll think about it
;) ... I never ever want to break 2.2, and such an update will definitively
break things. 2.2 took a long time to become that stable like it is now and it
can be broke within minutes. A no-go!
For users who need/want/experiment with that stuff there is still my
2.2-secure tree.
Anyway, 2.2 needs the hashing exploit fix ASAP ;)
ciao, Marc
next prev parent reply other threads:[~2003-08-27 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
[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
2003-08-22 17:46 ` Mike Fedyk
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=200308280034.19050.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=adefacc@tin.it \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=ruben@puettmann.net \
--cc=vherva@niksula.hut.fi \
/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
all inboxes | Powered by JetHome®