LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Brian Gerst <bgerst@didntduck.org>
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 15:53:27 -0500	[thread overview]
Message-ID: <20040518205326.GG28735@waste.org> (raw)
In-Reply-To: <40AA70B6.1050405@didntduck.org>

On Tue, May 18, 2004 at 04:23:18PM -0400, Brian Gerst wrote:
> 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.

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?

-- 
Matt Mackall : http://www.selenic.com : Linux development and consulting

  reply	other threads:[~2004-05-18 20:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-16 17:50 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 [this message]
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=20040518205326.GG28735@waste.org \
    --to=mpm@selenic.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=bgerst@didntduck.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.org \
    --subject='Re: [patch] kill off PC9800' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).