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. 035bdc56110914329c860870e338463793fb5597 Date: Wed, 27 May 2020 08:22:18 +0000 (GMT) [thread overview] Message-ID: <20200527082218.DBCE2386F425@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 035bdc56110914329c860870e338463793fb5597 (commit) from 57a146a0ce26e9eef1ecc1034689edb4c5412c3f (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 035bdc56110914329c860870e338463793fb5597 Author: Martin Liska <mliska@suse.cz> Date: Wed May 27 10:22:01 2020 +0200 Document gcc-commit-mklog hook. diff --git a/htdocs/gitwrite.html b/htdocs/gitwrite.html index e3a1305b..b9bcb768 100644 --- a/htdocs/gitwrite.html +++ b/htdocs/gitwrite.html @@ -436,6 +436,8 @@ repository:</p> <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> + <li><i>gcc-commit-mklog</i> - commit a git revision with a pre-filled + ChangeLog template</li> </ul> <p>The final customization that the script makes is to add a diff rule so ----------------------------------------------------------------------- Summary of changes: htdocs/gitwrite.html | 2 ++ 1 file changed, 2 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-05-27 8:22 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=20200527082218.DBCE2386F425@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: linkBe 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).