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. ea117d9202946863fe38484e8fe156c876c366d7 Date: Mon, 16 Oct 2023 07:57:11 +0000 (GMT) [thread overview] Message-ID: <20231016075711.9CFC7385771E@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 ea117d9202946863fe38484e8fe156c876c366d7 (commit) from e6c058387b10879f88b8a09607f5f286a1f3bc4e (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 ea117d9202946863fe38484e8fe156c876c366d7 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Mon Oct 16 09:56:26 2023 +0200 conduct: Use <img=...> instead of <img=... /> On the way break overly long lines. diff --git a/htdocs/conduct-faq.html b/htdocs/conduct-faq.html index 9ac65fbc..06f579b9 100644 --- a/htdocs/conduct-faq.html +++ b/htdocs/conduct-faq.html @@ -63,7 +63,8 @@ your question either, email <a href="mailto:conduct@gcc.gnu.org">conduct@gcc.gnu.org</a> with any additional questions or feedback.</p> -<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png" /></a><br> +<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"> +<img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png"></a><br> This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/"> Creative Commons Attribution-ShareAlike 4.0 International License</a>. diff --git a/htdocs/conduct-report.html b/htdocs/conduct-report.html index 58e4489e..1913185b 100644 --- a/htdocs/conduct-report.html +++ b/htdocs/conduct-report.html @@ -113,7 +113,8 @@ directly to another member, or to a member of the Steering Committee.</p> of the committee's decision. To make such a request, contact a member of the Steering Committee with your request and motivation.</p> -<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png" /></a><br> +<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"> +<img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png"></a><br> This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/"> Creative Commons Attribution-ShareAlike 4.0 International License</a>. diff --git a/htdocs/conduct-response.html b/htdocs/conduct-response.html index a261554d..42509828 100644 --- a/htdocs/conduct-response.html +++ b/htdocs/conduct-response.html @@ -132,7 +132,8 @@ excluded from the response process. For these cases, anyone can make a report directly to any of the committee members, as documented in the reporting guidelines.</p> -<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png" /></a><br> +<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"> +<img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png"></a><br> This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/"> Creative Commons Attribution-ShareAlike 4.0 International License</a>. diff --git a/htdocs/conduct.html b/htdocs/conduct.html index 25790035..e04188de 100644 --- a/htdocs/conduct.html +++ b/htdocs/conduct.html @@ -114,7 +114,8 @@ email <a href="mailto:conduct@gcc.gnu.org">conduct@gcc.gnu.org</a>.</p> that doesn't answer your questions, feel free to <a href="mailto:conduct@gcc.gnu.org">contact us</a>.</p> -<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png" /></a><br> +<a rel="license" href="http://creativecommons.org/licenses/by-sa/4.0/"> +<img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-sa/4.0/88x31.png"></a><br> This work is licensed under a <a rel="license" href="https://creativecommons.org/licenses/by-sa/4.0/"> Creative Commons Attribution-ShareAlike 4.0 International License</a>. ----------------------------------------------------------------------- Summary of changes: htdocs/conduct-faq.html | 3 ++- htdocs/conduct-report.html | 3 ++- htdocs/conduct-response.html | 3 ++- htdocs/conduct.html | 3 ++- 4 files changed, 8 insertions(+), 4 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2023-10-16 7:57 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=20231016075711.9CFC7385771E@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).