From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: GCC Administrator <gccadmin@sourceware.org>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>, overseers@sourceware.org
Subject: Re: gcc-10-20200308 is now available
Date: Mon, 9 Mar 2020 10:51:58 +0000 [thread overview]
Message-ID: <CAH6eHdRyW4fEMPiJn7K4bYJgxeq_Y65PA-qH8GYuyDjKKjYdSA@mail.gmail.com> (raw)
In-Reply-To: <20200308224550.92ABE387700E@server2.sourceware.org>
On Sun, 8 Mar 2020 at 22:48, GCC Administrator wrote:
>
> Snapshot gcc-10-20200308 is now available on
> https://gcc.gnu.org/pub/gcc/snapshots/10-20200308/
> and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
>
> This snapshot has been generated from the GCC 10 git branch
> with the following options: git://gcc.gnu.org/git/gcc.git branch master revision 9de42a8e995451cb13dceb3970ae23ff88240bff
>
> You'll find:
>
> gcc-10-20200308.tar.xz Complete GCC
>
> SHA256=cbd1498fcba449649142411ddcfc2bd08b52b8dccd0539a64af82ab13d54f5bf
> SHA1=41dce5595797f5bf7f59e87f9cba696d98857f29
Is it expected that
https://gcc.gnu.org/pub/gcc/snapshots/10-20200308/sha512.sum is not
present?
There is a sha512.sum file in previous snapshot dirs.
>
> Diffs from 10-20200301 are available in the diffs/ subdirectory.
>
> When a particular snapshot is ready for public consumption the LATEST-10
> link is updated and a message is sent to the gcc list. Please do not use
> a snapshot before it has been announced that way.
next parent reply other threads:[~2020-03-09 10:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200308224550.92ABE387700E@server2.sourceware.org>
2020-03-09 10:51 ` Jonathan Wakely [this message]
2020-03-09 14:37 ` Frank Ch. Eigler
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=CAH6eHdRyW4fEMPiJn7K4bYJgxeq_Y65PA-qH8GYuyDjKKjYdSA@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gccadmin@sourceware.org \
--cc=overseers@sourceware.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).