From: James Bottomley <James.Bottomley@steeleye.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Brian Gerst <bgerst@didntduck.org>, Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: [patch] kill off PC9800
Date: 18 May 2004 16:14:00 -0500 [thread overview]
Message-ID: <1084914841.1763.51.camel@mulgrave> (raw)
In-Reply-To: <20040518205326.GG28735@waste.org>
On Tue, 2004-05-18 at 15:53, Matt Mackall wrote:
> Actually it's a matter of fail to attempt to compile, which is
> different than fail to compile. The principle is the same - stick
> advance notice in a highly visible place where users are likely to see
> it. That place is _not_ this mailing list.
>
> We've had the code for years, and it would be nice to delete it if
> it's truly dead. But it seems silly to wake up one morning and say "no
> one's touched it for a year" and post a patch to delete it that same
> day. If it wasn't urgent yesterday, then why is it urgent today?
I would agree if it were a complete feature, but it's not. PC9800
cannot be selected for compilation in the current kernel. Without an
external patch set, it cannot be compiled or used. As far as I can
tell, it's always been like that.
I think the best way of making someone sit up and take notice is simply
to remove it. After all, given that we have the kernel under source
control it's not like it's going to be hard to put it back if someone
actually does notice and screams...
James
next prev parent reply other threads:[~2004-05-18 21:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-16 17:50 [patch] kill off PC9800 James Bottomley
2004-05-16 21:21 ` Andrew Morton
2004-05-16 21:28 ` Jeff Garzik
2004-05-16 21:38 ` James Bottomley
2004-05-17 17:15 ` Jeff Garzik
2004-05-18 20:14 ` Matt Mackall
2004-05-18 20:23 ` Brian Gerst
2004-05-18 20:53 ` Matt Mackall
2004-05-18 21:14 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-05-16 7:35 Norman Diamond
2004-05-16 16:36 ` Adrian Bunk
2004-05-17 21:38 ` Norman Diamond
2004-05-17 21:51 ` Roland Dreier
2004-05-17 21:59 ` Norman Diamond
2004-05-17 22:33 ` Bartlomiej Zolnierkiewicz
2004-05-18 1:04 ` viro
2004-05-17 22:17 ` Joel Jaeggli
2004-05-16 6:21 Randy.Dunlap
2004-05-16 6:28 ` Andrew Morton
2004-05-16 16:16 ` GOTO Masanori
2004-05-16 17:25 ` Randy.Dunlap
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=1084914841.1763.51.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rddunlap@osdl.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