public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. ad4e4e330fcfa5ec9043114aae9e4c295cb49ad3 Date: Tue, 20 Apr 2021 09:37:40 +0000 (GMT) [thread overview] Message-ID: <20210420093740.ABCCD3858C27@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 ad4e4e330fcfa5ec9043114aae9e4c295cb49ad3 (commit) from a58d9ae4c5ed59d90ec8fa1a21d836e182018adc (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 ad4e4e330fcfa5ec9043114aae9e4c295cb49ad3 Author: Martin Liska <mliska@suse.cz> Date: Tue Apr 20 11:36:37 2021 +0200 Remove part about coordination with FSF. diff --git a/htdocs/releasing.html b/htdocs/releasing.html index d51d6fc7..cb7bb5fe 100644 --- a/htdocs/releasing.html +++ b/htdocs/releasing.html @@ -121,9 +121,6 @@ to point to the online-documentation for the branch.</li> and info-gnu@gnu.org mailing lists. <ul> <li>Make sure that most mirrors have retrieved the new release already.</li> -<!-- John Sullivan <johns@fsf.org> is the FSF contact person --> -<li>In the case of a major release, coordinate announcements with the -FSF.</li> </ul></li> </ol> ----------------------------------------------------------------------- Summary of changes: htdocs/releasing.html | 3 --- 1 file changed, 3 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-04-20 9:37 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=20210420093740.ABCCD3858C27@sourceware.org \ --to=marxin@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).