public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 8be05148b4190ad49ceefb9bac0a75113c1aaa55
Date: Wed, 10 Jun 2020 13:46:35 +0000 (GMT)	[thread overview]
Message-ID: <20200610134635.536403851C3B@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  8be05148b4190ad49ceefb9bac0a75113c1aaa55 (commit)
      from  1dd508534fb35f65bceecc64145a4a8baf4765db (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 8be05148b4190ad49ceefb9bac0a75113c1aaa55
Author: Martin Liska <mliska@suse.cz>
Date:   Wed Jun 10 15:46:10 2020 +0200

    gcc-changelog: document additional authors

diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html
index 6ae962ea..a08ddcbb 100644
--- a/htdocs/codingconventions.html
+++ b/htdocs/codingconventions.html
@@ -171,7 +171,8 @@ a large batch of changes.</p>
     <li>script automatically generates missing "New file." entries for files that are added in a commit</li>
     <li>changed files that are not mentioned in a ChangeLog file generate an error</li>
     <li>similarly for unchanged files that are mentioned in a ChangeLog file</li>
-    <li>a commit author and committer date stamp can be automatically deduced from a git commit - we recommend to use it</li>
+    <li>a commit author and committer date stamp can be automatically deduced from a git commit
+        (additional authors are taken from Co-Authored-By trailer) - we recommend to use it</li>
     <li><code>co_authored_by</code> is added to each ChangeLog entry</li>
     <li>a PR component is checked against list of valid components</li>
     <li><code>ChangeLog</code> files, <code>DATESTAMP</code>, <code>BASE-VER</code> and <code>DEV-PHASE</code> can be modified only separately from other files</li>

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-06-10 13:46 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=20200610134635.536403851C3B@sourceware.org \
    --to=marxin@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).