public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 69102e7bf8c4afdc6380e0e6547c84cc5649eae5 Date: Wed, 19 Oct 2022 14:12:02 +0000 (GMT) [thread overview] Message-ID: <20221019141202.815113858D39@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 69102e7bf8c4afdc6380e0e6547c84cc5649eae5 (commit) from d857139eb40bbda4d056d0afbae61995d9c08bab (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 69102e7bf8c4afdc6380e0e6547c84cc5649eae5 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Wed Oct 19 16:11:10 2022 +0200 codingconventions: Fix two typos diff --git a/htdocs/codingconventions.html b/htdocs/codingconventions.html index c793058f..9d0a3f14 100644 --- a/htdocs/codingconventions.html +++ b/htdocs/codingconventions.html @@ -142,7 +142,7 @@ a large batch of changes.</p> supported formats: <code>a/b/c/ChangeLog</code>, <code>a/b/c/ChangeLog:</code>, <code>a/b/c/</code> (where ChangeLog file lives in the folder), <code>\ta/b/c/</code> and <code>a/b/c</code></li> <li><code>pr_entry</code> - bug report reference <br> example: <code>\tPR component/12345</code></li> - <li><code>changelog_file</code> - a modified file mentined in a ChangeLog: + <li><code>changelog_file</code> - a modified file mentioned in a ChangeLog: supported formats: <code>\t* a/b/c/file.c:</code>, <code>\t* a/b/c/file.c (function):</code>, <code>\t* a/b/c/file1.c, a/b/c/file2.c:</code></li> <li><code>changelog_file_comment</code> - line that follows a <code>changelog_file</code> with description of changes in the file; must start with <code>\t</code></li> @@ -154,7 +154,7 @@ a large batch of changes.</p> <h3>Format rules</h3> <ul> - <li><code>git_description</code> - optional; ends right before one of the other compoments is found</li> + <li><code>git_description</code> - optional; ends right before one of the other components is found</li> <li><code>committer_timestamp</code> - optional; when found before a <code>changelog_file</code>, then it is added to each changelog entry</li> <li><code>additional_author</code> - optional</li> ----------------------------------------------------------------------- Summary of changes: htdocs/codingconventions.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-10-19 14:12 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=20221019141202.815113858D39@sourceware.org \ --to=gerald@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).