From: bert hubert <ahu@ds9a.nl>
To: Chuck Wolber <chuckw@quantumlinux.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Development Model
Date: Tue, 19 Apr 2005 16:20:23 +0200 [thread overview]
Message-ID: <20050419142023.GA14968@outpost.ds9a.nl> (raw)
In-Reply-To: <Pine.LNX.4.60.0504182219360.6679@bailey.quantumlinux.com>
> that (at least for now) no *MAJOR* "rip it out, stomp on it, burn it and
> start over" parts of the kernel exist any longer? In other words, do you
These ideas continue to exist. This is partly due to increasing skills of
developers but also to the changing environment. You'll find literally
scores of commits that say 'this was a good idea when were were limited to
1024 filedescriptor' or the like.
I think the tty layer has been ready to be ripped out and replaced for the
past 10 years though.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
next prev parent reply other threads:[~2005-04-19 14:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 5:31 Chuck Wolber
2005-04-19 14:20 ` bert hubert [this message]
2005-04-19 14:50 ` Arjan van de Ven
2005-04-19 19:24 ` Rik van Riel
2005-04-20 20:22 ` Ralf Baechle
2005-04-19 20:26 ` Florian Weimer
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=20050419142023.GA14968@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=chuckw@quantumlinux.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
Powered by JetHome