public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [wwwdocs] Broken links
@ 2013-11-20  9:08 Philippe Baril Lecavalier
  2013-11-20  9:36 ` Tobias Burnus
  2013-11-20 16:53 ` Philippe Baril Lecavalier
  0 siblings, 2 replies; 8+ messages in thread
From: Philippe Baril Lecavalier @ 2013-11-20  9:08 UTC (permalink / raw)
  To: gcc-patches; +Cc: gerald

[-- Attachment #1: Type: TEXT/PLAIN, Size: 408 bytes --]


Enclosed is a patch modifying three broken links, on three separate
pages. I also added some indications to about.html on how to submit a
patch for the web site for those who do not have commit access, which is
precisely what I have been instructed to do (so now it becomes
documented).

See <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59184> for more
information.

All the best,

Philippe Baril Lecavalier

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: Type: TEXT/X-PATCH; NAME=broken_links_patch.diff, Size: 3443 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 04:55:23 -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 04:55:23 -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 04:55:23 -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 04:55:23 -0000
@@ -69,6 +69,24 @@
 list.</li>
 </ol>
 
+<p>If you do not have commit access, please 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 the following:</p>
+
+<ul>
+<li> Secify <code>[wwwwdocs]</code> in the subject header.</li>
+
+<li> Description of your patch and list of modified files.</li>
+
+<li> Mention the fact that you do not have commit access (why you do
+this).</li>
+
+<li> Link to <a href="http://gcc.gnu.org/bugzilla/">bugzilla</a>
+issue, if applicable.</li>
+
+<li> Your patch (from <code>cvs diff</code>) as an attachment.</li>
+</ul>
 
 <h2 id="system">The host system</h2>
 

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [wwwdocs] Broken links
  2013-11-20  9:08 [wwwdocs] Broken links Philippe Baril Lecavalier
@ 2013-11-20  9:36 ` Tobias Burnus
  2013-11-20 11:33   ` Patrick Marlier
  2013-11-20 16:53 ` Philippe Baril Lecavalier
  1 sibling, 1 reply; 8+ messages in thread
From: Tobias Burnus @ 2013-11-20  9:36 UTC (permalink / raw)
  To: Philippe Baril Lecavalier, gcc-patches; +Cc: gerald

Am 20.11.2013 06:00, schrieb Philippe Baril Lecavalier:
> +<p>If you do not have commit access, please 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 the following:</p>
> +
> +<ul>
> +<li> Secify <code>[wwwwdocs]</code> in the subject header.</li>

"Specify"

> +<li> Description of your patch and list of modified files.</li>
> +
> +<li> Mention the fact that you do not have commit access (why you do
> +this).</li>

I don't understand sentence in parenthesis. Should they explain why they 
don't have commit access? Note that even with commit access one also 
sends patches to gcc-patches@ for review; hence, there is no real 
difference in this regard.

Tobias

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [wwwdocs] Broken links
  2013-11-20  9:36 ` Tobias Burnus
@ 2013-11-20 11:33   ` Patrick Marlier
       [not found]     ` <CABu4Xf5po3_aa=dbEV3c05kotSGdrK9X8xrqzOoTsT=-PWmmWw@mail.gmail.com>
  0 siblings, 1 reply; 8+ messages in thread
From: Patrick Marlier @ 2013-11-20 11:33 UTC (permalink / raw)
  To: Tobias Burnus; +Cc: Philippe Baril Lecavalier, GCC Patches, gerald

+<li> Secify <code>[wwwwdocs]</code> in the subject header.</li>

Also [wwwdocs] instead of [wwwwdocs].

--
Patrick Marlier

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [wwwdocs] Broken links
  2013-11-20  9:08 [wwwdocs] Broken links Philippe Baril Lecavalier
  2013-11-20  9:36 ` Tobias Burnus
@ 2013-11-20 16:53 ` Philippe Baril Lecavalier
  1 sibling, 0 replies; 8+ messages in thread
From: Philippe Baril Lecavalier @ 2013-11-20 16:53 UTC (permalink / raw)
  To: gcc-patches; +Cc: gerald

[-- 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>
 

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [wwwdocs] Broken links
       [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
  2 siblings, 0 replies; 8+ messages in thread
From: Tobias Burnus @ 2013-11-20 19:30 UTC (permalink / raw)
  To: Philippe Baril Lecavalier, GCC Patches; +Cc: gerald, Patrick Marlier

Am 20.11.2013 16:45, schrieb Philippe Baril Lecavalier:
> 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.

Well, stating that one doesn't have commit access is useful. Thus with:

"<li> Mention the fact that you do not have commit access"

I was perfectly happy. I was mainly struggling with what followed those 
words:

"(why you do this)."

First, I don't quite understand the meaning of the second part. 
Secondly, one meaning I can read into it is misleading. Just removing 
the "(Â…)" would be fine with me

Anyway, I leave the wordsmithing to Gerald and you.

Tobias

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [wwwdocs] Broken links
       [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
  2 siblings, 0 replies; 8+ messages in thread
From: Gerald Pfeifer @ 2015-04-07 10:31 UTC (permalink / raw)
  To: Philippe Baril Lecavalier; +Cc: GCC Patches, Tobias Burnus, Patrick Marlier

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>

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [wwwdocs] Broken links
       [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
  2 siblings, 1 reply; 8+ messages in thread
From: Gerald Pfeifer @ 2015-04-09 21:48 UTC (permalink / raw)
  To: Philippe Baril Lecavalier; +Cc: GCC Patches, Tobias Burnus, Patrick Marlier

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.

Thank you Phillipe!  I just committed the readings.html portion
of your patch which fixes the long standing broken link.

Apologies again for nobody picking up your fine patches 
originally -- please do not hesitate to send more, I promise
we'll do better.

I decided not to go with the changes to about.html, since the
documentation there and re the web pages in general has changed
a bit, but you inspired me to (hopefully) improve things a bit
more on that front, and I'll shortly apply a somewhat related
patch and will copy you on that.

Thanks again,
Gerald

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>
 

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: [wwwdocs] Broken links
  2015-04-09 21:48       ` Gerald Pfeifer
@ 2015-07-21  6:05         ` P.B. Lecavalier
  0 siblings, 0 replies; 8+ messages in thread
From: P.B. Lecavalier @ 2015-07-21  6:05 UTC (permalink / raw)
  To: Gerald Pfeifer, Gerald Pfeifer; +Cc: GCC Patches

On 04/09/2015 05:47 PM, Gerald Pfeifer wrote:
> Thank you Phillipe!  I just committed the readings.html portion
> of your patch which fixes the long standing broken link.
> 
> Apologies again for nobody picking up your fine patches 
> originally -- please do not hesitate to send more, I promise
> we'll do better.
> 
> I decided not to go with the changes to about.html, since the
> documentation there and re the web pages in general has changed
> a bit, but you inspired me to (hopefully) improve things a bit
> more on that front, and I'll shortly apply a somewhat related
> patch and will copy you on that.
> 
> Thanks again,
> Gerald

That's nice. I just mysteriously stumbled on that message from you...
probably in the same way that you found mine from a while ago. For the
about.html, from the moment that it inspired you some improvements, them
I'm happy.

Cheers,

P.B. Lecavalier

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2015-07-21  1:58 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-20  9:08 [wwwdocs] Broken links 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 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).