From: Philippe Baril Lecavalier <pbl.ltx@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: gerald@pfeifer.com
Subject: Re: [wwwdocs] Broken links
Date: Wed, 20 Nov 2013 16:53:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1311201049001.21337@zardoz.site> (raw)
In-Reply-To: <alpine.LNX.2.00.1311192052400.15744@zardoz.site>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 203 bytes --]
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.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: TEXT/x-patch; name=broken_links_patch.diff, Size: 3235 bytes --]
Index: projects/beginner.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/beginner.html,v
retrieving revision 1.57
diff -u -r1.57 beginner.html
--- projects/beginner.html 29 Dec 2012 00:24:56 -0000 1.57
+++ projects/beginner.html 20 Nov 2013 15:13:58 -0000
@@ -32,7 +32,7 @@
<a href="http://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="http://gcc.gnu.org/onlinedocs/gccint/Trees.html">incomplete, C/C++ specific manual</a>.</p>
+href="http://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: projects/documentation.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/projects/documentation.html,v
retrieving revision 1.5
diff -u -r1.5 documentation.html
--- projects/documentation.html 19 Sep 2007 22:40:29 -0000 1.5
+++ projects/documentation.html 20 Nov 2013 15:13:58 -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="http://gcc.gnu.org/onlinedocs/gccint/Trees.html">C/C++ specific manual</a>,
+href="http://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>
Index: readings.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/readings.html,v
retrieving revision 1.233
diff -u -r1.233 readings.html
--- readings.html 31 Oct 2013 18:03:28 -0000 1.233
+++ readings.html 20 Nov 2013 15:13:58 -0000
@@ -401,7 +401,7 @@
<h3>Objective-C Information</h3>
<ul>
- <li><a href="http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/">
+ <li><a href="https://developer.apple.com/library/mac/documentation/cocoa/conceptual/ProgrammingWithObjectiveC/Introduction/Introduction.html">
Objective-C Language Description</a> (Apple Computer)</li>
</ul>
Index: about.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/about.html,v
retrieving revision 1.19
diff -u -r1.19 about.html
--- about.html 18 Aug 2013 20:38:58 -0000 1.19
+++ about.html 20 Nov 2013 15:13:58 -0000
@@ -69,6 +69,14 @@
list.</li>
</ol>
+<p>Whether or not you have commit access, you must send an email to <a
+ href="mailto:gcc-patches@gcc.gnu.org">gcc-patches@gcc.gnu.org</a>
+and CC <a href="mailto:gerald@pfeifer.com">gerald@pfeifer.com</a>,
+with your patch as an attachment. Specify [wwwdocs] in the subject
+header and follow the instructions on <a
+ href="http://gcc.gnu.org/contribute.html#patches">patch
+ submission</a>, whenever applicable.</p>
+
<h2 id="system">The host system</h2>
prev parent reply other threads:[~2013-11-20 15:52 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
2015-04-09 21:48 ` Gerald Pfeifer
2015-07-21 6:05 ` P.B. Lecavalier
2013-11-20 16:53 ` Philippe Baril Lecavalier [this message]
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.LNX.2.00.1311201049001.21337@zardoz.site \
--to=pbl.ltx@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).