public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Segher Boessenkool <segher@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 57190618a8884fbf1ae7f48a6968dab84b2837fa Date: Sat, 27 Feb 2021 00:00:54 +0000 (GMT) [thread overview] Message-ID: <20210227000054.A77A0386F807@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 57190618a8884fbf1ae7f48a6968dab84b2837fa (commit) from 7722a0767da7afcf5966b692aba8e3f6669cd35b (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 57190618a8884fbf1ae7f48a6968dab84b2837fa Author: Segher Boessenkool <segher@kernel.crashing.org> Date: Fri Feb 26 23:55:42 2021 +0000 Fix typo (mklog -> mklog.py) in codingconventions.html diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html index f6842c8f..7577528d 100644 --- a/htdocs/codingconventions.html +++ b/htdocs/codingconventions.html @@ -115,7 +115,7 @@ maintained and kept up to date. In particular:</p> <p> ChangeLog entries are part of git commit messages and are automatically put into a corresponding ChangeLog file. A ChangeLog template can be easily generated -with <code>./contrib/mklog</code> script. GCC offers a checking script that +with <code>./contrib/mklog.py</code> script. GCC offers a checking script that verifies a proper ChangeLog formatting (see <code>git gcc-verify</code> git alias). for a particular git commit. The checking script covers most commonly used ChangeLog formats and the following paragraphs explain what it supports. ----------------------------------------------------------------------- Summary of changes: htdocs/codingconventions.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-02-27 0:00 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=20210227000054.A77A0386F807@sourceware.org \ --to=segher@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).