From: Phil Edwards <phil@jaj.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: Stan Shebs <shebs@apple.com>, Richard Henderson <rth@redhat.com>,
gcc@gcc.gnu.org
Subject: Re: deprecate i960 now?
Date: Thu, 03 Oct 2002 18:48:00 -0000 [thread overview]
Message-ID: <20021003205022.B27093@disaster.jaj.com> (raw)
In-Reply-To: <200210040018.g940Iac02570@piper.synopsys.com>; from jbuck@synopsys.com on Thu, Oct 03, 2002 at 05:18:36PM -0700
On Thu, Oct 03, 2002 at 05:18:36PM -0700, Joe Buck wrote:
> If we have no maintainer and no i960 processors, and the gdb folks are
> taking away resources, we can't maintain it. We can have an alternate
> designation in such cases, "orphaned" rather than "deprecated", meaning
> it's on hold until volunteers step up to the challenge of keeping it
> going.
[...]
> Agreed, which is why an "orphaned" status might be better. The code can
> stay around, but maintainance goes on hold until someone takes it over.
I don't understand the advantage of keeping code in the tree that we
know doesn't work, or at least /will/ break given that there's nobody
maintaining it. Surely a future interested developer can fetch the last-
known-working version of i960 code from CVS with not much difficulty.
Phil
--
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002
next prev parent reply other threads:[~2002-10-04 0:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-03 11:32 Richard Henderson
2002-10-03 11:40 ` Mike Stump
2002-10-03 12:13 ` Stan Shebs
2002-10-03 12:19 ` Branko Čibej
2002-10-03 11:44 ` Stan Shebs
2002-10-03 17:35 ` Joe Buck
2002-10-03 18:48 ` Phil Edwards [this message]
2002-10-03 22:32 ` Stan Shebs
2002-10-04 9:55 ` Jim Wilson
2002-10-03 17:37 Robert Dewar
2002-10-04 9:46 ` Jim Wilson
2002-10-04 6:28 Robert Dewar
2002-10-04 11:30 ` Richard Henderson
2002-10-05 5:56 Robert Dewar
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=20021003205022.B27093@disaster.jaj.com \
--to=phil@jaj.com \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=rth@redhat.com \
--cc=shebs@apple.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).