public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: gerald@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 25b8efaa9b5f4c8d95f1510296ead31113d44ea8 Date: Thu, 23 Jan 2020 08:40:00 -0000 [thread overview] Message-ID: <20200123084020.34132.qmail@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 25b8efaa9b5f4c8d95f1510296ead31113d44ea8 (commit) from 7f294acb3db3c6db8df1e1a160aa7c5c3f35258a (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 25b8efaa9b5f4c8d95f1510296ead31113d44ea8 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Jan 23 09:39:42 2020 +0100 Abstract a statement to refer to our infrastructure, no specifics. diff --git a/htdocs/contribute.html b/htdocs/contribute.html index 042ff069..b671354e 100644 --- a/htdocs/contribute.html +++ b/htdocs/contribute.html @@ -186,7 +186,7 @@ be plaintext rather than part of the patch since the top of the ChangeLog changes rapidly and a patch to the ChangeLog would probably no longer apply by the time your patch is reviewed. If your change fixes a PR, put text in the ChangeLog entry mentioning -the PR. The <code>svn commit</code> machinery understands how to +the PR. Our infrastructure understands how to extract this information and automatically append the commit log to the PR. In order to be recognized, the text must fit a particular form. It must start with "PR", and then must include the category ----------------------------------------------------------------------- Summary of changes: htdocs/contribute.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-01-23 8:40 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=20200123084020.34132.qmail@sourceware.org \ --to=gerald@gcc.gnu.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).