On Fri, Jul 17, 2020 at 09:10:45AM +0200, Richard Biener wrote:
> On Fri, 17 Jul 2020, Thomas Schwinge wrote:
>
> > Hi!
> >
> > On 2020-07-15T13:50:35+0200, Richard Biener <rguent...@suse.de> wrote:
> > > The first release candidate for GCC 10.2 is available from
> > >
> > > https://gcc.gnu.org/pub/gcc/snapshots/10.2.0-RC-20200715/
> > > ftp://gcc.gnu.org/pub/gcc/snapshots/10.2.0-RC-20200715/
> > >
> > > and shortly its mirrors. It has been generated from git commit
> > > 932e9140d3268cf2033c1c3e93219541c53fcd29.
> >
> > That's probably something to be careful about for any tarball etc.
> > releases: per that commit 932e9140d3268cf2033c1c3e93219541c53fcd29, we
> > don't have complete 'ChangeLog' files state -- the "catch-up" commit
> > 25f8c7101d1a1e7304ed53ec727240a88eb65086 "Daily bump" (2020-07-16) was
> > not included.
>
> Not so important for the release candidate but indeed for last minutes
> commit to the branch before the actual release
> https://gcc.gnu.org/releasing.html doesn't list how to manually invoke
> ChangeLog updating.
>
> Of ocurse I'm just hoping we won't have any last-minute checkins ;)
Actually,
contrib/gcc-changelog/git_update_version.py -c
should be able to do it now, I just didn't get top adding it to gcc_release
yet.
Jakub
