public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: other/931: VMS support looks bitrotten
Date: Sat, 11 Jan 2003 23:16:00 -0000	[thread overview]
Message-ID: <20030111231601.3151.qmail@sources.redhat.com> (raw)

The following reply was made to PR other/931; it has been noted by GNATS.

>From jsm28@cam.ac.uk  Mon Jan 13 01:02:23 2003
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <neroden@gcc.gnu.org>,  <gcc-bugs@gcc.gnu.org>,  <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: other/931: VMS support looks bitrotten
Date: Sat, 11 Jan 2003 23:06:19 +0000 (GMT)

 On 11 Jan 2003 neroden@gcc.gnu.org wrote:
 
 >     VAX/VMS support is being dropped for 3.4 and we've stripped out
 > most, if not all, of its files.
 
 There's just the documentation in install-old.texi for the old VMS build 
 system to remove.  (Note that the install manual is quite fragile, with 
 all the @node links manually specified, and changes in other bits of the 
 manual might be needed along with the removal.  When removing those docs 
 it will be necessary to test all of DVI, info and HTML (the 
 install.texi2html script) generation for the install manual.)
 
 Quite possibly some of vms.texi is also out of date; the VMS maintainer
 ought to look over that file and update it as necessary.
 
 -- 
 Joseph S. Myers
 jsm28@cam.ac.uk
 


             reply	other threads:[~2003-01-11 23:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-11 23:16 Joseph S. Myers [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-11 22:44 neroden
2002-12-28  4:26 Joseph S. Myers
2002-12-27 22:16 Nathanael Nerode
2002-04-02  3:26 Joseph S. Myers
2002-04-02  1:22 neil

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=20030111231601.3151.qmail@sources.redhat.com \
    --to=jsm28@cam.ac.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).