From: "Douglas B Rupp" <rupp@gnat.com>
To: "Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: "Gerald Pfeifer" <pfeifer@dbai.tuwien.ac.at>,
"Lisa M. Opus Goldstein" <opus@gnu.org>, <gcc@gcc.gnu.org>,
<gcc-patches@gcc.gnu.org>
Subject: [PATCH] Remove VMS section in documentation (was Re: HEADS UP: GCC manual soon to be printed)
Date: Fri, 23 May 2003 17:59:00 -0000 [thread overview]
Message-ID: <01d101c32153$a21e1af0$6901a8c0@Jinx> (raw)
In-Reply-To: <Pine.LNX.4.53.0305212126400.20386@kern.srcf.societies.cam.ac.uk>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
> In that case, could you submit a patch that removes vms.texi (and the glue
> in gcc.texi that uses it), or, as the case may be, removes from vms.texi
> everything that is irrelevant leaving only anything that still applies to
> the Alpha port?
>
Attached is the simple patch. I am unable to test it due to configuration
problems that I don't have time to sort out right now. It seems safe enough
though. OK to commit in trunk and 3.3 branch?
[-- Attachment #2: novms.diff.txt --]
[-- Type: text/plain, Size: 960 bytes --]
* doc/gcc.texi: Remove VMS section.
* doc/vms.texi: Obsolete.
Index: gcc/doc/gcc.texi
===================================================================
RCS file: /cvs/gcc/gcc/gcc/doc/gcc.texi,v
retrieving revision 1.59
diff -u -p -r1.59 gcc.texi
--- gcc/doc/gcc.texi 4 Feb 2003 01:27:45 -0000 1.59
+++ gcc/doc/gcc.texi 23 May 2003 17:34:42 -0000
@@ -153,7 +153,6 @@ Introduction, gccint, GNU Compiler Colle
* Bugs:: How, why and where to report bugs.
* Service:: How to find suppliers of support for GCC.
* Contributing:: How to contribute to testing and developing GCC.
-* VMS:: Using GCC on VMS.
* Funding:: How to help assure funding for free software.
* GNU Project:: The GNU Project and GNU/Linux.
@@ -178,7 +177,6 @@ Introduction, gccint, GNU Compiler Colle
@include bugreport.texi
@include service.texi
@include contribute.texi
-@include vms.texi
@include funding.texi
@include gnu.texi
next prev parent reply other threads:[~2003-05-23 17:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-01 23:38 HEADS UP: GCC manual soon to be printed Gerald Pfeifer
2003-04-02 20:47 ` Joseph S. Myers
2003-04-03 4:32 ` Zack Weinberg
2003-04-03 5:48 ` Janis Johnson
2003-04-03 6:16 ` Neil Booth
2003-04-03 7:54 ` Zack Weinberg
2003-04-03 8:39 ` Joseph S. Myers
2003-04-08 19:06 ` Janis Johnson
2003-05-15 10:22 ` Gerald Pfeifer
2003-05-15 14:23 ` Lisa M. Opus Goldstein
2003-05-18 22:31 ` Joseph S. Myers
2003-05-15 22:14 ` Joseph S. Myers
2003-05-21 20:24 ` Joseph S. Myers
2003-05-21 20:28 ` Douglas B Rupp
2003-05-21 20:41 ` Joseph S. Myers
2003-05-23 17:59 ` Douglas B Rupp [this message]
2003-05-22 19:06 ` Lisa M. Opus Goldstein
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='01d101c32153$a21e1af0$6901a8c0@Jinx' \
--to=rupp@gnat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
--cc=opus@gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).