public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mikael Morin <morin-mikael@orange.fr>
To: Jerry D <jvdelisle2@gmail.com>,
	Jerry DeLisle <jvdelisle@protonmail.com>,
	gfortran <fortran@gcc.gnu.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch, gfortran.dg] Adjust numerous tests so that they pass on line endings
Date: Sat, 28 Jan 2023 17:44:33 +0100	[thread overview]
Message-ID: <30e3819f-4f25-5b7d-e1e6-3f08c7df6cff@orange.fr> (raw)
In-Reply-To: <3b171e9e-4c55-599c-7812-6081fc726843@gmail.com>

Le 28/01/2023 à 03:47, Jerry D a écrit :
> 
> It is not apparent to me that the testsuite/ChangeLog was updated. Maybe 
> there is a time delay on that?
> 
Yes, it's done daily as part of the "daily bump" commit.
You can see it in the git log:

$ git log -- gcc/testsuite/ChangeLog
commit f457a62e63a86d5e5342eda16538a26355199856
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Tue Jan 17 00:18:06 2023 +0000

     Daily bump.

commit 5013c3bb3ead9c27adb90152115ca1d606cbf2dc
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Sun Jan 15 00:17:49 2023 +0000

     Daily bump.

commit ecd637e9761485437498f311ddf09af5286d6d0f
Author: GCC Administrator <gccadmin@gcc.gnu.org>
Date:   Fri Jan 13 00:17:18 2023 +0000

     Daily bump.



      reply	other threads:[~2023-01-28 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-21  2:13 Jerry DeLisle
2023-01-21 23:59 ` Jerry D
2023-01-22  5:28   ` NightStrike
2023-01-22 13:38   ` Mikael Morin
2023-01-22 16:06     ` Jerry D
2023-01-28  2:47     ` Jerry D
2023-01-28 16:44       ` Mikael Morin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=30e3819f-4f25-5b7d-e1e6-3f08c7df6cff@orange.fr \
    --to=morin-mikael@orange.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle2@gmail.com \
    --cc=jvdelisle@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).