From: Gerald Pfeifer <gerald@pfeifer.com>
To: Philippe Baril Lecavalier <pbl.ltx@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Tobias Burnus <burnus@net-b.de>,
Patrick Marlier <patrick.marlier@gmail.com>
Subject: Re: [wwwdocs] Broken links
Date: Tue, 07 Apr 2015 10:31:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1504071229260.9357@tuna.site> (raw)
In-Reply-To: <CABu4Xf5po3_aa=dbEV3c05kotSGdrK9X8xrqzOoTsT=-PWmmWw@mail.gmail.com>
Hi Philippe,
On Wed, 20 Nov 2013, Philippe Baril Lecavalier wrote:
> Embarrassing typos, my apologies. I was told to specify that I don't
> have commit access, but since this mention is irrelevant, I modified my
> suggested notice in about.html to reflect that. See attached.
sorry for the delay, somehow this fell through the cracks.
I just applied the first part of your patchset after adjusting
http to https that we are now using by default (so that the patch
applies).
Gerald
Index: beginner.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v
retrieving revision 1.61
diff -u -r1.61 beginner.html
--- beginner.html 29 Jun 2014 11:31:33 -0000 1.61
+++ beginner.html 7 Apr 2015 10:29:22 -0000
@@ -31,7 +31,7 @@
<a href="https://gcc.gnu.org/onlinedocs/gccint/RTL.html">RTL</a>.
It may help to understand the higher-level <code>tree</code> structure as
well. Unfortunately, for this we only have an <a
-href="https://gcc.gnu.org/onlinedocs/gccint/Trees.html">incomplete, C/C++ specific manual</a>.</p>
+href="https://gcc.gnu.org/onlinedocs/gccint/GENERIC.html">incomplete, C/C++ specific manual</a>.</p>
<p>Remember to <a href="../contributewhy.html">keep other developers
informed</a> of any substantial projects you intend to work on.</p>
Index: documentation.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/documentation.html,v
retrieving revision 1.9
diff -u -r1.9 documentation.html
--- documentation.html 29 Jun 2014 11:31:33 -0000 1.9
+++ documentation.html 7 Apr 2015 10:29:22 -0000
@@ -56,7 +56,7 @@
<p>We've got quite a bit of this but it is scattered all over the
place. It belongs in the official manual. There is a <a
-href="https://gcc.gnu.org/onlinedocs/gccint/Trees.html">C/C++ specific manual</a>,
+href="https://gcc.gnu.org/onlinedocs/gccint/GENERIC.html">C/C++ specific manual</a>,
which is incomplete, though. The file
<code>gcc/LANGUAGES</code> contains incomplete and outdated information
about changes made in not so recent years to the <code>tree</code>
next prev parent reply other threads:[~2015-04-07 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 9:08 Philippe Baril Lecavalier
2013-11-20 9:36 ` Tobias Burnus
2013-11-20 11:33 ` Patrick Marlier
[not found] ` <CABu4Xf5po3_aa=dbEV3c05kotSGdrK9X8xrqzOoTsT=-PWmmWw@mail.gmail.com>
2013-11-20 19:30 ` Tobias Burnus
2015-04-07 10:31 ` Gerald Pfeifer [this message]
2015-04-09 21:48 ` Gerald Pfeifer
2015-07-21 6:05 ` P.B. Lecavalier
2013-11-20 16:53 ` Philippe Baril Lecavalier
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=alpine.LSU.2.20.1504071229260.9357@tuna.site \
--to=gerald@pfeifer.com \
--cc=burnus@net-b.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=patrick.marlier@gmail.com \
--cc=pbl.ltx@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).