* [PATCH, doc] Update fortran file locations
@ 2019-06-09 17:24 Maya Rashish
2019-06-15 21:13 ` Gerald Pfeifer
0 siblings, 1 reply; 2+ messages in thread
From: Maya Rashish @ 2019-06-09 17:24 UTC (permalink / raw)
To: gcc-patches
doc/invoke.texi: Update fortran file locations.
---
gcc/doc/invoke.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index 5e3e8873d35..f1d22e87cbc 100644
--- a/gcc/doc/invoke.texi
+++ b/gcc/doc/invoke.texi
@@ -29242,7 +29242,7 @@ Like @samp{%g}, except if @option{-pipe} is in effect. In that case
all. These are the two most common ways to instruct a program that it
should read from standard input or write to standard output. If you
need something more elaborate you can use an @samp{%@{pipe:@code{X}@}}
-construct: see for example @file{f/lang-specs.h}.
+construct: see for example @file{gcc/fortran/lang-specs.h}.
@item %.@var{SUFFIX}
Substitutes @var{.SUFFIX} for the suffixes of a matched switch's args
--
2.21.0
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH, doc] Update fortran file locations
2019-06-09 17:24 [PATCH, doc] Update fortran file locations Maya Rashish
@ 2019-06-15 21:13 ` Gerald Pfeifer
0 siblings, 0 replies; 2+ messages in thread
From: Gerald Pfeifer @ 2019-06-15 21:13 UTC (permalink / raw)
To: Maya Rashish; +Cc: gcc-patches
On Sun, 9 Jun 2019, Maya Rashish wrote:
> doc/invoke.texi: Update fortran file locations.
Thank you. I added a full ChangeLog entry and committed this to
trunk.
If I had more time, I'd push back to the GCC 9 branch as well;
anyone who wants to pick doc changes and push them?
Gerald
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-15 21:13 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-06-09 17:24 [PATCH, doc] Update fortran file locations Maya Rashish
2019-06-15 21:13 ` Gerald Pfeifer
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).