From: Gerald Pfeifer <gerald@pfeifer.com>
To: Richard Biener <richard.guenther@gmail.com>,
Jakub Jelinek <jakub@redhat.com>
Cc: Andrew Engelbrecht <sudoman@ninthfloor.org>,
gcc@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [PATCH] for Re: netgull.com mirror doesn't have gcc release .sig files.
Date: Sat, 24 Feb 2018 19:19:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1802230935520.4782@anthias.pfeifer.com> (raw)
In-Reply-To: <CAFiYyc1h3xOS8SVoKsrrs-Dgwry9EV0NueOdbJcYNti9OJxXTQ@mail.gmail.com>
On Tue, 8 Jul 2014, Richard Biener wrote:
>> The reason you do not see .sig files on our netgull.com mirror is
>> that it mirrors gcc.gnu.org, which does not carry those, whereas
>> ftp.gnu.org and hence its mirrors has them.
>>
>> Richi, Jakub, can you also add those .sig files to the copies on
>> gcc.gnu.org going forward?
> Nothing against that ... can you add an action item to releasing.html
> please?
Done thusly.
Sorry for the delay (ahem).
Gerald
Index: releasing.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v
retrieving revision 1.48
diff -u -r1.48 releasing.html
--- releasing.html 17 Jan 2018 13:10:17 -0000 1.48
+++ releasing.html 23 Feb 2018 07:54:01 -0000
@@ -60,6 +60,9 @@
<li>Upload the release to ftp.gnu.org.</li>
+<li>Ensure that the upload on gcc.gnu.org also comes with
+cryptographic signatures (<code>.sig</code> files).</li>
+
<li>Increment the version number in <code>gcc/BASE-VER</code>.
<code>gcc/DEV-PHASE</code> remains empty. Check the file in.</li>
prev parent reply other threads:[~2018-02-24 19:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 23:20 Andrew Engelbrecht
2014-07-05 21:29 ` Gerald Pfeifer
2014-07-08 9:01 ` Richard Biener
2018-02-24 19:19 ` Gerald Pfeifer [this message]
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=alpine.LSU.2.21.1802230935520.4782@anthias.pfeifer.com \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
--cc=sudoman@ninthfloor.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).