Re: gcc/DATESTAMP wasn't updated since 20240507

2024-05-13 Thread Rainer Orth
Richard Biener writes: > On Thu, 9 May 2024, Jakub Jelinek wrote: > >> On Thu, May 09, 2024 at 12:14:43PM +0200, Jakub Jelinek wrote: >> > On Thu, May 09, 2024 at 12:04:38PM +0200, Rainer Orth wrote: >> > > I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, >> > > staying at

Re: gcc/DATESTAMP wasn't updated since 20240507

2024-05-10 Thread Richard Biener
On Thu, 9 May 2024, Jakub Jelinek wrote: > On Thu, May 09, 2024 at 12:14:43PM +0200, Jakub Jelinek wrote: > > On Thu, May 09, 2024 at 12:04:38PM +0200, Rainer Orth wrote: > > > I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, > > > staying at 20240507. > > > > I think it is

Re: gcc/DATESTAMP wasn't updated since 20240507

2024-05-09 Thread Jakub Jelinek
On Thu, May 09, 2024 at 12:14:43PM +0200, Jakub Jelinek wrote: > On Thu, May 09, 2024 at 12:04:38PM +0200, Rainer Orth wrote: > > I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, > > staying at 20240507. > > I think it is because of the r15-268 commit, we do support > This

Re: gcc/DATESTAMP wasn't updated since 20240507

2024-05-09 Thread Jakub Jelinek
On Thu, May 09, 2024 at 12:04:38PM +0200, Rainer Orth wrote: > I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, > staying at 20240507. I think it is because of the r15-268 commit, we do support This reverts commit ... when the referenced commit contains a ChangeLog message,

gcc/DATESTAMP wasn't updated since 20240507

2024-05-09 Thread Rainer Orth
I just noticed that gcc/DATESTAMP wasn't updated yesterday and today, staying at 20240507. Rainer -- - Rainer Orth, Center for Biotechnology, Bielefeld University