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. cf6ceb538ac57dc95e6aac741c9c7ada5f4cfee4
Date: Fri, 27 Jan 2023 00:20:07 +0000 (GMT)	[thread overview]
Message-ID: <20230127002007.DF3773858D20@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  cf6ceb538ac57dc95e6aac741c9c7ada5f4cfee4 (commit)
      from  8fb92c2b989db3d72bb2b8db41b3231b5497e678 (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 cf6ceb538ac57dc95e6aac741c9c7ada5f4cfee4
Author: Gerald Pfeifer <gerald@pfeifer.com>
Date:   Fri Jan 27 01:19:44 2023 +0100

    codingconventions: Update a link to Github docs

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index af08f11a..24365815 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -147,7 +147,7 @@ a large batch of changes.</p>
     <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-and-editing-commits/creating-a-commit-with-multiple-authors">GitHub format</a>
+        href="https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/creating-a-commit-with-multiple-authors">GitHub format</a>
         for a Co-Authored-By</li>
 </ul>
 

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

Summary of changes:
 htdocs/codingconventions.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-01-27  0:20 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=20230127002007.DF3773858D20@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).