gcc-8-20171210 is now available

2017-12-10 Thread gccadmin
Snapshot gcc-8-20171210 is now available on
  ftp://gcc.gnu.org/pub/gcc/snapshots/8-20171210/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.

This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 255534

You'll find:

 gcc-8-20171210.tar.xzComplete GCC

  SHA256=3cca5f13b09064bfffa2a8243a3fa1a873f4f6cbe619205d6ff2c3318f3b7d08
  SHA1=b30fdd6397607c2e5fb0015a3de2fe0ffc23c93a

Diffs from 8-20171203 are available in the diffs/ subdirectory.

When a particular snapshot is ready for public consumption the LATEST-8
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.


Re: Finishing the repository conversion

2017-12-10 Thread Jason Merrill
On Sat, Dec 9, 2017 at 11:45 PM, Eric S. Raymond  wrote:
> (I tried to send an earlier version of this a few days ago.  It's not
> in your list archives; an MTA somewhere might have had a bad moment.)
>
> I have good news and better news.
>
> The good news is both reposurgeon bugs known to be blocking the GCC
> repository conversion seem now to be fixed.
>
> The better news is that the person cutting my paychecks has approved
> the GCC repo conversion as a supported activity, which means I can
> concentrate on this until it's done.  This couldn't happen sooner
> because NTPsec had to get to 1.0 first.

Great!

> I'm mirroring the repo now. It would  helpful if I could get an
> up-to-date copy of the repository's attribution map (usernames to full
> names and email addresses).

I've pushed to the thyrsus gcc-conversion repository the rest of my
work from last year, including a few changes to the attribution map
and a post-processing script.

It has occurred to me that for the period since the creation of
gcc.gnu.org we might just use @gcc.gnu.org addresses (which are likely
to forward) rather than try to nail down everyone's current address.
But using the address from the ChangeLog sounds better.

> One thing my software can do now that it couldn't do six months ago
> is mine Author fields from ChangeLog histories.  So you'll get a
> better-quality conversion than if I had been able to finish this then.

Excellent.

Jason