Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: Re: [5.1/rfc] Obsolete MPW host
Date: Thu, 10 May 2001 08:32:00 -0000	[thread overview]
Message-ID: <3AF9A211.90801@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1010422092113.13269G-100000@is>

Did I reply to this?

> I'm a bit worried by this removal of support for systems which are
> deemed old/unmaintained/whatever, although I understand how leaving
> them in the code base could hamper development.  However, imagine
> someone who just happens to need a working GDB version on one of these
> platforms--it could be next to impossible getting there, and the
> better job we do at cleanup, the harder it will be.

The old files and configurations are available in either CVS, or, for 
for the really old stuff, in the GDB archives (on the FTP site).


> So how about adding to the distribution a file that would list, for
> each platform whose support was discontinued, the last GDB version
> that was known to build and work on that platform?  This would at
> least allow people to fetch such an old version, build it, use it, and
> maybe retrofit that support into the current sources using the old
> version as the base

Hopefully people can figure this out from the NEWS file.  Each 
target/system should have an entry recording when it was added and when 
it was deleted (a few don't though).

	Andrew



  reply	other threads:[~2001-05-10  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3ADCD1D5.9AA0B1AC@cygnus.com>
2001-04-21 15:54 ` Andrew Cagney
2001-04-21 23:20   ` Eli Zaretskii
2001-05-10  8:32     ` Andrew Cagney [this message]
2001-05-10  8:59       ` Eli Zaretskii

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=3AF9A211.90801@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb-patches@sourceware.cygnus.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