Re: Commit messages and the move to git

[Joseph Myers <joseph@codesourcery.com>]

On Thu, 19 Dec 2019, Jonathan Wakely wrote:

> On Thu, 19 Dec 2019 at 15:49, Joseph Myers <joseph@codesourcery.com> wrote:
> >
> > On Thu, 19 Dec 2019, Richard Earnshaw (lists) wrote:
> >
> > > > Done. https://gitlab.com/esr/gcc-conversion/merge_requests/25 fixes
> > > > (most of?) the most egregious ones, like fortran fixes with c++ PR
> > > > numbers and vice versa. Jakub and I have several whitelist commits
> > > > too, but I think they're all less critical (as mentioned previously,
> > > > most of them are unimportant differences like rtl-optimization vs
> > > > tree-optimization, or debug vs lto, or simply that  the Bugzilla
> > > > component has been changed since the commit was done and the commit
> > > > was actually right at the time).
> > > >
> > >
> > > Merged
> >
> > And I've fixed up some Python syntax there (commas that needed to be
> > colons, between the commit number and the fixup information).
> 
> Thanks.
> 
> I'm afraid it was too mind-numbing to just work through the list from
> bottom to top. Jakub and I found some problems and some that can be
> whitelisted. I submitted another merge request.

Thanks, merged.

If people have done updates to components in Bugzilla and want a fresh 
list generated using fresh Bugzilla data and the updates to component 
aliases, I can readily do that (using the file of commit messages left 
behind from my last conversion run), load on sourceware permitting.

-- 
Joseph S. Myers
joseph@codesourcery.com