public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. d7f86129184f9981930148fbe1a5e5075abcef02
Date: Thu, 15 Oct 2020 07:41:29 +0000 (GMT)	[thread overview]
Message-ID: <20201015074129.119483857810@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".

The branch, master has been updated
       via  d7f86129184f9981930148fbe1a5e5075abcef02 (commit)
       via  72b6ee4021a45fbd8a844f6e39e02b7995d31f66 (commit)
      from  07ba0ba22103a9702e8ae63662eb659984bcc8f0 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d7f86129184f9981930148fbe1a5e5075abcef02
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Oct 15 09:40:35 2020 +0200

    Update Co-Authored-By referece on GitHub.

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index 162e1dda..f6842c8f 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -145,7 +145,9 @@ a large batch of changes.</p>
         supported formats: <code>\t* a/b/c/file.c:</code>, <code>\t* a/b/c/file.c (function):</code>, <code>\t* a/b/c/file1.c, a/b/c/file2.c:</code></li>
     <li><code>changelog_file_comment</code> - line that follows a <code>changelog_file</code> with description of changes in the file;
         must start with <code>\t</code></li>
-    <li><code>co_authored_by</code> - <a href="https://docs.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors">GitHub format</a> for a Co-Authored-By</li>
+    <li><code>co_authored_by</code> - <a
+        href="https://docs.github.com/en/free-pro-team@latest/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors">GitHub format</a>
+        for a Co-Authored-By</li>
 </ul>
 
 <h3>Format rules</h3>

commit 72b6ee4021a45fbd8a844f6e39e02b7995d31f66
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Thu Oct 15 09:38:08 2020 +0200

    Switch Edsger W. Dijkstra's page to https.

diff --git a/htdocs/readings.html b/htdocs/readings.html
index 4162d9f9..f1bc116d 100644
--- a/htdocs/readings.html
+++ b/htdocs/readings.html
@@ -500,7 +500,7 @@ names.
        Computer Science</a> by Karl Kleine
      </li>
 
-     <li><a href="http://www.cs.utexas.edu/users/EWD/">The writings of Edsger W. Dijkstra (RIP)</a></li>
+     <li><a href="https://www.cs.utexas.edu/users/EWD/">The writings of Edsger W. Dijkstra (RIP)</a></li>
    </ul>
    </li>
 

-----------------------------------------------------------------------

Summary of changes:
 htdocs/codingconventions.html | 4 +++-
 htdocs/readings.html          | 2 +-
 2 files changed, 4 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-10-15  7:41 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=20201015074129.119483857810@sourceware.org \
    --to=gerald@sourceware.org \
    --cc=gcc-cvs-wwwdocs@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).