[ Developmen Plan Timeline ] 9.2 Release Date
Hello! I noticed something that I think is a typo over the gcc development plan timeline found here: https://gcc.gnu.org/develop.html#timeline The 9.2 gcc release appears to have been on 2019.02.12, which I think it should have been 2019.08.12 Alin Lupu
Re: GCC wwwdocs move to git done
On Wed, 9 Oct 2019, Joseph Myers wrote: > I've done the move of GCC wwwdocs to git (using the previously posted and > discussed scripts), including setting up the post-receive hook to do the > same things previously covered by the old CVS hooks, and minimal updates > to the web pages dealing with the CVS setup for wwwdocs. Really, really, cool. Thanks a huge bunch, Joseph! > Note 2: changes may be needed to the process for updating www.gnu.org > and Gerald's validator. The validator *should* be working in this new world now. And I am in contact with webmas...@gnu.org and will update this round as things evolve. (Not an urgency, just important.) Gerald
Re: git conversion of GCC wwwdocs repository
On Wed, 25 Sep 2019, Jonathan Wakely wrote: > I mean that there's not much value in having my past commits listed as > coming from various "different" authors: > > Jonathan Wakely > Jonathan Wakely > Jonathan Wakely > Jonathan Wakely > Jonathan Wakely > > All of those "identities" are the same person, so making all my > commits use the same Author is arguably correct, even if I was using > different addresses at different times. In my case that address really is ger...@pfeifer.com (which I should keep for the rest of my life). I noticed today that old commits show up as ger...@gcc.gnu.org, whereas those from after the conversion show up as ger...@pfeifer.com. Is there a way to unify that to ger...@pfeifer.com throughout? Gerald
Re: git conversion of GCC wwwdocs repository
On Okt 20 2019, Gerald Pfeifer wrote: > I noticed today that old commits show up as ger...@gcc.gnu.org, whereas > those from after the conversion show up as ger...@pfeifer.com. Is there > a way to unify that to ger...@pfeifer.com throughout? See "MAPPING AUTHORS" in git-shortlog(1). Andreas. -- Andreas Schwab, sch...@linux-m68k.org GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1 "And now for something completely different."
gcc-10-20191020 is now available
Snapshot gcc-10-20191020 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/10-20191020/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 10 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 277217 You'll find: gcc-10-20191020.tar.xz Complete GCC SHA256=606f47c22f66c0f9ee8bd661c41666bce7ac74c2a43bb6292afa17d875ca2d67 SHA1=db1d6507c86cd79185b6922fbd09b4a3cfc3cabb Diffs from 10-20191013 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.
