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. d9963372ca42baa9836921ec1be85d1dbfae0cb9
Date: Wed, 20 May 2020 12:52:46 +0000 (GMT)	[thread overview]
Message-ID: <20200520125246.236DF3851C25@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  d9963372ca42baa9836921ec1be85d1dbfae0cb9 (commit)
      from  1498f1d49b73c4ce3ffb1c886a4b70daa51cf66c (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 d9963372ca42baa9836921ec1be85d1dbfae0cb9
Author: Martin Liska <mliska@suse.cz>
Date:   Wed May 20 10:12:44 2020 +0200

    Mention new git aliases.

diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html
index 791213a5..e3a1305b 100644
--- a/htdocs/gitwrite.html
+++ b/htdocs/gitwrite.html
@@ -433,7 +433,9 @@ repository:</p>
   </li>
   <li><i>gcc-descr</i> - Undocumented</li>
   <li><i>gcc-undescr</i> - Undocumented</li>
-  <li><i>gcc-verify</i> - Undocumented</li>
+  <li><i>gcc-verify</i> - verify ChangeLog format for a particular commit</li>
+  <li><i>gcc-backport</i> - alias for <code>git cherry-pick -x</code></li>
+  <li><i>gcc-mklog</i> - generate a ChangeLog template for a patch</li>
 </ul>
 
 <p>The final customization that the script makes is to add a diff rule so

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

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


hooks/post-receive
-- 
gcc-wwwdocs


                 reply	other threads:[~2020-05-20 12:52 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=20200520125246.236DF3851C25@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).