public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Jason Merrill <jason@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. da867d3952a6852f28a31e073cb99835958bd02a Date: Tue, 20 Jun 2023 16:42:04 +0000 (GMT) [thread overview] Message-ID: <20230620164204.6F6403858D1E@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 da867d3952a6852f28a31e073cb99835958bd02a (commit) from 36a9a45a1f5bc4e49d8a15c60b425921584b1fc1 (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 da867d3952a6852f28a31e073cb99835958bd02a Author: Jason Merrill <jason@redhat.com> Date: Tue Jun 20 12:41:39 2023 -0400 bugs: Correct link to Code of Conduct diff --git a/htdocs/bugs/index.html b/htdocs/bugs/index.html index c068560f..813b78c0 100644 --- a/htdocs/bugs/index.html +++ b/htdocs/bugs/index.html @@ -124,7 +124,7 @@ three of which can be obtained from the output of <code>gcc -v</code>:</p> certain constructs that are not GCC extensions. Ask them in forums dedicated to the discussion of the programming language.</li> - <li>Violations of the <a href="conduct.html">Code of Conduct</a>.</li> + <li>Violations of the <a href="../conduct.html">Code of Conduct</a>.</li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/bugs/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-06-20 16:42 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=20230620164204.6F6403858D1E@sourceware.org \ --to=jason@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).