From: Adrian Bunk <bunk@kernel.org>
To: David Newall <davidn@davidnewall.com>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for mm] Remove iBCS support
Date: Thu, 24 Jan 2008 19:24:14 +0200 [thread overview]
Message-ID: <20080124172414.GD4476@does.not.exist> (raw)
In-Reply-To: <4798C511.8070305@davidnewall.com>
On Fri, Jan 25, 2008 at 03:34:17AM +1030, David Newall wrote:
> Adrian Bunk wrote:
> > But Linux kernel development is not driven by people producing hot air
> > about what they wish to see in the future, Linux kernel development is
> > driven by people sending patches.
>
> Removal of code is not development. It's the opposite of development.
Removing dead code makes:
- the kernel smaller,
- the kernel faster and
- makes it easier to maintain the non-dead code.
All of these are considered useful by the people who actually
contribute to the Linux kernel.
> At one stage iBCS2 support DID work. Now it doesn't. Now there's an
> argument that the remaining infrastructure should be removed. This is
> the wrong direction to take.
When did iBCS2 support work in a plain ftp.kernel.org kernel?
And if you consider iBCS2 support that important I can only repeat that
the language on Linux kernel are patches, not hot air.
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:[~2008-01-24 17:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 4:59 [PATCH for mm] Remove iBCS support Andi Kleen
2008-01-20 2:27 ` David Newall
2008-01-20 3:11 ` Andi Kleen
2008-01-20 4:46 ` David Newall
2008-01-20 5:18 ` Andi Kleen
2008-01-20 5:33 ` David Newall
2008-01-20 5:55 ` Andi Kleen
2008-01-20 6:23 ` David Newall
2008-01-20 7:29 ` Andi Kleen
2008-01-21 1:37 ` David Newall
2008-01-22 10:24 ` Karl Kiniger
2008-01-22 15:06 ` David Newall
2008-01-22 15:52 ` Adrian Bunk
2008-01-23 8:48 ` Andi Kleen
2008-01-23 14:12 ` Karl Kiniger
2008-01-23 14:24 ` Andi Kleen
2008-01-24 17:06 ` David Newall
2008-01-22 11:12 ` Ingo Molnar
2008-01-22 12:42 ` Karl Kiniger
2008-01-22 15:13 ` David Newall
2008-01-22 15:49 ` Ingo Molnar
2008-01-24 17:01 ` David Newall
2008-01-22 16:01 ` Adrian Bunk
2008-01-24 17:04 ` David Newall
2008-01-24 17:24 ` Adrian Bunk [this message]
2008-01-24 17:55 ` David Newall
2008-01-24 18:14 ` Adrian Bunk
2008-01-25 2:14 ` David Newall
2008-01-25 5:12 ` Valdis.Kletnieks
2008-01-25 16:40 ` Alan Cox
2008-01-24 19:51 ` Pavel Machek
2008-01-25 2:17 ` David Newall
2008-01-24 20:37 ` Andi Kleen
2008-01-25 2:16 ` David Newall
2008-01-22 16:50 ` Alan Cox
2008-01-24 17:08 ` David Newall
2008-01-22 13:20 ` Giulio
2008-01-20 13:06 ` Alan Cox
2008-01-20 13:43 ` David Newall
2008-01-20 13:51 ` Alan Cox
2008-01-25 12:17 ` Ingo Molnar
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=20080124172414.GD4476@does.not.exist \
--to=bunk@kernel.org \
--cc=akpm@osdl.org \
--cc=andi@firstfloor.org \
--cc=davidn@davidnewall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.