public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/sphinx] Revert @ifset DEVELOPMENT changes.
Date: Tue, 20 Apr 2021 08:02:31 +0000 (GMT) [thread overview]
Message-ID: <20210420080231.5111D38515E2@sourceware.org> (raw)
https://gcc.gnu.org/g:a78721691fb18b5b490c87e3e7464711e0381ca1
commit a78721691fb18b5b490c87e3e7464711e0381ca1
Author: Martin Liska <mliska@suse.cz>
Date: Tue Apr 20 10:01:18 2021 +0200
Revert @ifset DEVELOPMENT changes.
Diff:
---
gcc/fortran/gfc-internals.texi | 8 ++++----
gcc/fortran/gfortran.texi | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/gcc/fortran/gfc-internals.texi b/gcc/fortran/gfc-internals.texi
index 21cd0229384..49de0cee30f 100644
--- a/gcc/fortran/gfc-internals.texi
+++ b/gcc/fortran/gfc-internals.texi
@@ -102,11 +102,11 @@ Boston, MA 02110-1301, USA@*
This manual documents the internals of @command{gfortran},
the GNU Fortran compiler.
-ifsetDEVELOPMENT
+@ifset DEVELOPMENT
@emph{Warning:} This document, and the compiler it describes, are still
under development. While efforts are made to keep it up-to-date, it might
not accurately reflect the status of the most recent GNU Fortran compiler.
-endifset
+@end ifset
@comment
@comment When you add a new menu item, please keep the right hand
@@ -139,12 +139,12 @@ endifset
This manual documents the internals of @command{gfortran}, the GNU Fortran
compiler.
-ifsetDEVELOPMENT
+@ifset DEVELOPMENT
@emph{Warning:} This document, and the compiler it describes, are still
under development. While efforts are made to keep it up-to-date, it
might not accurately reflect the status of the most recent GNU Fortran
compiler.
-endifset
+@end ifset
@end iftex
At present, this manual is very much a work in progress, containing
diff --git a/gcc/fortran/gfortran.texi b/gcc/fortran/gfortran.texi
index 319b65c6250..60bf257cbf2 100644
--- a/gcc/fortran/gfortran.texi
+++ b/gcc/fortran/gfortran.texi
@@ -161,11 +161,11 @@ This manual documents the use of @command{gfortran},
the GNU Fortran compiler. You can find in this manual how to invoke
@command{gfortran}, as well as its features and incompatibilities.
-ifsetDEVELOPMENT
+@ifset DEVELOPMENT
@emph{Warning:} This document, and the compiler it describes, are still
under development. While efforts are made to keep it up-to-date, it might
not accurately reflect the status of the most recent GNU Fortran compiler.
-endifset
+@end ifset
@comment
@comment When you add a new menu item, please keep the right hand
@@ -212,12 +212,12 @@ This manual documents the use of @command{gfortran}, the GNU Fortran
compiler. You can find in this manual how to invoke @command{gfortran},
as well as its features and incompatibilities.
-ifsetDEVELOPMENT
+@ifset DEVELOPMENT
@emph{Warning:} This document, and the compiler it describes, are still
under development. While efforts are made to keep it up-to-date, it
might not accurately reflect the status of the most recent GNU Fortran
compiler.
-endifset
+@end ifset
@end iftex
The GNU Fortran compiler front end was
reply other threads:[~2021-04-20 8:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210420080231.5111D38515E2@sourceware.org \
--to=marxin@gcc.gnu.org \
--cc=gcc-cvs@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).