On Nov 10, 2024, Jakub Jelinek wrote:
> On Sun, Nov 10, 2024 at 01:30:06PM -0300, Alexandre Oliva wrote:
>> I'm surprised the commit-time checker didn't catch them.
> I'm surprised too, but don't want to try to push further broken commits just
> to double check that. ;)
You can leave that test
On Sun, 10 Nov 2024, Jakub Jelinek wrote:
> On Sun, Nov 10, 2024 at 01:30:06PM -0300, Alexandre Oliva wrote:
> > On Nov 9, 2024, Jakub Jelinek wrote:
> >
> > > r15-4998 and r15-5004 had wrong commit message, add those to
> > > ignored commits.
> >
> > Ugh, sorry and thanks.
> > Was that .c vs
On Sun, Nov 10, 2024 at 01:30:06PM -0300, Alexandre Oliva wrote:
> On Nov 9, 2024, Jakub Jelinek wrote:
>
> > r15-4998 and r15-5004 had wrong commit message, add those to
> > ignored commits.
>
> Ugh, sorry and thanks.
> Was that .c vs .cc only, or was there anything else?
I think so.
> I'm s
On Nov 9, 2024, Jakub Jelinek wrote:
> r15-4998 and r15-5004 had wrong commit message, add those to
> ignored commits.
Ugh, sorry and thanks.
Was that .c vs .cc only, or was there anything else?
I'm surprised the commit-time checker didn't catch them.
It used to, and that was very helpful to a
Hi!
r15-4998 and r15-5004 had wrong commit message, add those to
ignored commits. ChangeLog will need to be added manually.
The patch below is what I've committed before gcc_update_version
and attached patch after it to fix this up.
2024-11-09 Jakub Jelinek
* gcc-changelog/git_updat
