From: "szonyi calin" <caszonyi@yahoo.com>
To: "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org
Subject: Re: A users thoughts on the new dev. model
Date: Fri, 23 Jul 2004 17:24:21 +0200 (CEST) [thread overview]
Message-ID: <20040723152421.52282.qmail@web52904.mail.yahoo.com> (raw)
In-Reply-To: <cdr5i3$568$1@terminus.zytor.com>
--- "H. Peter Anvin" <hpa@zytor.com> a écrit : > Followup to:
<cdpee5$otu$1@gatekeeper.tmr.com>
> By author: Bill Davidsen <davidsen@tmr.com>
> In newsgroup: linux.dev.kernel
>
> Thus:
>
> - Andrew will put experimental patches into -mm;
> - Andrew will continue to forward-port 2.6 mainstream fixes
> to
> -mm;
> - Patches which have proven themselves stable and useful get
> backported to 2.6;
> - If the delta between 2.6 and -mm becomes too great we'll
> consider a hard fork AT THAT TIME, i.e. fork lazily instead
> of the past model of forking eagerly.
>
> Why the change? Because the model already has proven itself,
> and
> shown itself to be more functional than what we've had in the
> past.
> 2.6 is probably the most stable mainline tree we've had since
> 1.2 or
> so, and yet Linus and Andrew process *lots* of changes. The
> -mm tree
> has become a very effective filter for what should go into
> mainline,
> whereas the odd-number forks generally *haven't* been, because
> backporting to mainline has usually been an afterthought.
>
> I for one welcome our new -mm overlords.
>
> -hpa
Thank you for clarifying this.
So linux 2.6 from kernel.org stay stable.
And 2.6x-mm is like a 2.7 development tree (thought not that
experimental ;-) )
>From the LWM story i understood that linux will be like windows:
lots of "features" but no stability, except if you use a
distribution kernel. And that seriously made me think about
using another free *nix for a stable system.
Calin
=====
--
A mouse is a device used to point at
the xterm you want to type in.
Kim Alm on a.s.r.
Vous manquez despace pour stocker vos mails ?
Yahoo! Mail vous offre GRATUITEMENT 100 Mo !
Créez votre Yahoo! Mail sur http://fr.benefits.yahoo.com/
Le nouveau Yahoo! Messenger est arrivé ! Découvrez toutes les nouveautés pour dialoguer instantanément avec vos amis. A télécharger gratuitement sur http://fr.messenger.yahoo.com
next prev parent reply other threads:[~2004-07-23 15:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 15:04 Evan Hisey
2004-07-22 22:25 ` Bill Davidsen
2004-07-23 13:58 ` H. Peter Anvin
2004-07-23 15:24 ` szonyi calin [this message]
2004-07-23 16:39 ` David Ford
2004-07-23 19:06 ` Xiong Jiang
2004-07-23 20:00 ` Tim Wright
2004-07-23 21:40 ` Adrian Bunk
2004-07-23 23:04 ` hpa
2004-07-24 10:38 ` Adrian Bunk
2004-07-27 20:08 ` Bill Davidsen
2004-07-22 22:57 ` Paul Jackson
2004-07-27 20:20 ` Bill Davidsen
2004-07-28 7:31 ` Paul Jackson
2004-07-23 19:32 ` Florin Andrei
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=20040723152421.52282.qmail@web52904.mail.yahoo.com \
--to=caszonyi@yahoo.com \
--cc=hpa@zytor.com \
--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
all inboxes | Powered by JetHome®