public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. 002061bd9346602ae275171f90c883452d68f462
Date: Tue, 27 Apr 2021 10:22:48 +0000 (GMT) [thread overview]
Message-ID: <20210427102248.466F63894436@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 002061bd9346602ae275171f90c883452d68f462 (commit)
from 4debbf1dda6f26bfbc3dc93b7111b34bfacb252d (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 002061bd9346602ae275171f90c883452d68f462
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Apr 27 12:22:18 2021 +0200
List a new GPG key I'm using for signing releases.
diff --git a/htdocs/mirrors.html b/htdocs/mirrors.html
index 462d7cd7..7c86233e 100644
--- a/htdocs/mirrors.html
+++ b/htdocs/mirrors.html
@@ -68,6 +68,9 @@ Key fingerprint = 7F74 F97C 1034 68EE 5D75 0B58 3AB0 0996 FC26 A641
1024D/C3C45C06 2004-04-21 Jakub Jelinek <jakub@redhat.com><br />
Key fingerprint = 33C2 35A3 4C46 AA3F FB29 3709 A328 C3A2 C3C4 5C06
</li></ul>
+4096R/09B5FA62 2020-05-28 Jakub Jelinek <jakub@redhat.com><br />
+Key fingerprint = D3A9 3CAD 751C 2AF4 F8C7 AD51 6C35 B993 09B5 FA62
+</li></ul>
<p>If you wish to host a new mirror site, please contact
<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a>. Include the
-----------------------------------------------------------------------
Summary of changes:
htdocs/mirrors.html | 3 +++
1 file changed, 3 insertions(+)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2021-04-27 10:22 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=20210427102248.466F63894436@sourceware.org \
--to=jakub@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: link
Be 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).