From: Brian Gerst <bgerst@didntduck.org>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>,
James Bottomley <James.Bottomley@SteelEye.com>,
linux-kernel@vger.kernel.org, "Randy.Dunlap" <rddunlap@osdl.org>
Subject: Re: [patch] kill off PC9800
Date: Tue, 18 May 2004 16:23:18 -0400 [thread overview]
Message-ID: <40AA70B6.1050405@didntduck.org> (raw)
In-Reply-To: <20040518201416.GT5414@waste.org>
Matt Mackall wrote:
> On Sun, May 16, 2004 at 02:21:23PM -0700, Andrew Morton wrote:
>
>>James Bottomley <James.Bottomley@SteelEye.com> wrote:
>>
>>> Randy.Dunlap" <rddunlap@osdl.org> wrote:
>>> >
>>> > PC9800 sub-arch is incomplete, hackish (at least in IDE), maintainers
>>> > don't reply to emails and haven't touched it in awhile.
>>>
>>> And the hardware is obsolete, isn't it? Does anyone know when they were
>>> last manufactured, and how popular they are?
>>>
>>>Hey, just being obsolete is no grounds for eliminating a
>>>subarchitecture...
>>
>>Well it's a question of whether we're likely to see increasing demand for
>>it in the future. If so then it would be prudent to put some effort into
>>fixing it up rather than removing it.
>>
>>Seems that's not the case. I don't see a huge rush on this but if after
>>this discussion nobody steps up to take care of the code over the next few
>>weeks, it's best to remove it.
>
>
> Perhaps a nicer way to do this is to add a compile warning or error:
>
> #warning "arch/i386/mach-pc9800 unmaintained since xx/xx/xx, nominated
> for removal xx/xx/xx if unclaimed"
>
> ..where the second date is, say, 3+ months after the warning goes in.
> Then people can nominate stuff for removal with one liners and users
> will get ample opportunity to complain.
>
You're missing the point that this code doesn't compile *at all*.
Nobody would ever see the warning.
--
Brian Gerst
next prev parent reply other threads:[~2004-05-18 20:23 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 [this message]
2004-05-18 20:53 ` Matt Mackall
2004-05-18 21:14 ` James Bottomley
-- 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=40AA70B6.1050405@didntduck.org \
--to=bgerst@didntduck.org \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.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