public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 062897ff96bb9651f7a1e152bc2327cbda4ad89e
Date: Wed, 20 Dec 2023 23:09:44 +0000 (GMT)	[thread overview]
Message-ID: <20231220230944.0D38B386186F@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  062897ff96bb9651f7a1e152bc2327cbda4ad89e (commit)
      from  79b804a9bda634f0efad4fe15564d1b2374adb35 (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 062897ff96bb9651f7a1e152bc2327cbda4ad89e
Author: Jason Merrill <jason@redhat.com>
Date:   Mon Dec 11 22:10:53 2023 -0500

    gitwrite: add gcc-style

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 1ffda77a..0c146aba 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -432,9 +432,11 @@ repository:</p>
     output.  Of particular use is the
     <code>--oneline</code> option to summarize the commit on a single line.
   </li>
-  <li><i>gcc-descr</i> - Undocumented</li>
-  <li><i>gcc-undescr</i> - Undocumented</li>
+  <li><i>gcc-descr</i> - describe a commit relative to its first gcc release,
+    e.g. r12-1234</li>
+  <li><i>gcc-undescr</i> - convert a gcc-descr back to a commit SHA</li>
   <li><i>gcc-verify</i> - verify ChangeLog format for a particular commit</li>
+  <li><i>gcc-style</i> - verify coding style for a particular commit</li>
   <li><i>gcc-backport</i> - run script that does <code>git cherry-pick -x</code>
       and reverts all modifications of ChangeLog files (both from index
       and conflicting files)</li>

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

Summary of changes:
 htdocs/gitwrite.html | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)


hooks/post-receive
-- 
gcc-wwwdocs

                 reply	other threads:[~2023-12-20 23:09 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=20231220230944.0D38B386186F@sourceware.org \
    --to=jason@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).