From: Krzysztof Halasa <khc@pm.waw.pl>
To: Willy Tarreau <willy@w.ods.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Some thoughts about stable kernel development
Date: 12 Nov 2003 16:01:20 +0100 [thread overview]
Message-ID: <m3n0b18wcf.fsf@defiant.pm.waw.pl> (raw)
In-Reply-To: <20031109192954.GB1094@alpha.home.local>
Willy Tarreau <willy@w.ods.org> writes:
> - maintaining two trees is always more work than only one tree for the
> same person, whatever the changes. This is obviously true, otherwise
> none of us would ask for someone else to maintain the stable tree :-)
> I believe this reason was given by both Alan and Marcelo at different
> times.
Sure. However, with this scenario, the amount of additional work would be
low, as the time-consuming things are done once for both trees.
> - I think it was Linus who said that clueless people will only use distro's
> kernels, therefore are not affected by how the kernel is developped. And
> for other people like us, the "stable" kernel will never contain enough
> features and we will have to patch anyway.
Not sure about it - while I'm using 2.6.0test on my notebook (my personal
news/mail server + less important things), I also use official kernels
on some machines and patched trees on other ones.
What I _don't_ use is distribution kernel - not because it's bad, but
rather because i don't know it good enough.
> - someone else (alan ?) said that even most obvious fixes can break some
> setups, so there are not many "obviously riskless" patches around, and
> if there's a really critical one which needs to go mainstream very
> quickly,
> then the maintainer can always release a new version in a hurry and delay
> -preX pending features for the next release.
-post, yes. But it only solves this one problem.
--
Krzysztof Halasa, B*FH
next prev parent reply other threads:[~2003-11-12 15:07 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 18:41 Krzysztof Halasa
2003-11-09 19:05 ` Valdis.Kletnieks
2003-11-12 15:05 ` Krzysztof Halasa
2003-11-09 19:06 ` Stefan Smietanowski
2003-11-12 15:07 ` Krzysztof Halasa
2003-11-12 16:04 ` Stefan Smietanowski
2003-11-12 16:51 ` Krzysztof Halasa
2003-11-13 7:33 ` Stefan Smietanowski
2003-11-13 19:55 ` Krzysztof Halasa
2003-11-09 19:26 ` Andrew Morton
2003-11-09 20:34 ` Alan Cox
2003-11-09 20:41 ` Maciej Zenczykowski
2003-11-09 19:29 ` Willy Tarreau
2003-11-12 15:01 ` Krzysztof Halasa [this message]
2003-11-09 19:50 ` John Bradford
2003-11-09 23:49 ` Valdis.Kletnieks
2003-11-10 8:53 ` John Bradford
2003-11-09 23:54 ` Rob Landley
2003-11-10 8:50 ` John Bradford
2003-11-11 7:47 ` Ryan Anderson
2003-11-11 8:19 ` Valdis.Kletnieks
2003-11-11 8:53 ` John Bradford
2003-11-10 10:58 ` Marcelo Tosatti
2003-11-12 14:48 ` Krzysztof Halasa
2003-11-10 13:35 ` jlnance
2003-11-12 14:43 ` Krzysztof Halasa
2003-11-10 16:54 ` Adrian Bunk
2003-11-12 14:40 ` Krzysztof Halasa
2003-11-09 21:53 Matt
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=m3n0b18wcf.fsf@defiant.pm.waw.pl \
--to=khc@pm.waw.pl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=torvalds@osdl.org \
--cc=willy@w.ods.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
Powered by JetHome