From: Adrian Bunk <bunk@fs.tum.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A users thoughts on the new dev. model
Date: Fri, 23 Jul 2004 23:40:56 +0200 [thread overview]
Message-ID: <20040723214055.GR19329@fs.tum.de> (raw)
In-Reply-To: <cdr5i3$568$1@terminus.zytor.com>
On Fri, Jul 23, 2004 at 01:58:27PM +0000, H. Peter Anvin wrote:
> Followup to: <cdpee5$otu$1@gatekeeper.tmr.com>
> By author: Bill Davidsen <davidsen@tmr.com>
> In newsgroup: linux.dev.kernel
> >
> > I confess I feel that this new model is a return to the bad old days
> > when the stable tree wasn't. Sounds as if Andrew is bored with the idea
> > of letting 2.7 be the development tree and just being the gatekeeper of
> > STABLE new features for 2.6. Perhaps 2.7 should be opened and Andrew
> > will have a place to play, and features can drift to 2.6 more slowly.
> >
>
> I think the discussion we had at the kernel summit has been somewhat
> misrepresented by LWN et al. What we discussed was really more of a
> "soft fork", with the -mm tree serving the purpose of 2.7, rather than
> a hard fork with a separate maintainer and putting ourselves in
> back/forward-porting hell all over again.
>
> Note that Andrew's -mm tree *specificially* has infrastructure to keep
> changes apart and thus backporting to 2.6 mainstream of patches which
> have proven themselves becomes trivial.
>...
One problem from a user's point of view is that removal of obsolete code
that works sufficiently for some users.
Andrew said explicitely in a mail to linux-kernel that he'd consider
removing devfs "mid-2005" - and it didn't sound as if this would only be
a -mm "feature".
Even if 2.7 is started this doesn't has to imply that it has to be
flooded with big changes - a short 2.7 with relativley few invasive
changes might also be an option.
> -hpa
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-07-23 21:41 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
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 [this message]
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=20040723214055.GR19329@fs.tum.de \
--to=bunk@fs.tum.de \
--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®