public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry D <jvdelisle2@gmail.com>
To: Mikael Morin <morin-mikael@orange.fr>,
	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: Sun, 22 Jan 2023 08:06:38 -0800	[thread overview]
Message-ID: <9bac323a-89fe-5a0b-296b-57961b5f0d0d@gmail.com> (raw)
In-Reply-To: <4663046b-db95-5acd-fd08-8a14dcb7c67d@orange.fr>

On 1/22/23 5:38 AM, Mikael Morin wrote:
> Hello,
> 
> Le 22/01/2023 à 00:59, Jerry D via Fortran a écrit :
> (...)
>>
>> Proposed ChangeLog entry using git gcc-commit-mklog:
>>
>> Author: Jerry DeLisle <jvdelisle@gcc.gnu.org>
>> Date:   Sat Jan 21 15:47:19 2023 -0800
>>
>>      Revise the line end tests to pass on certain windows test 
>> environments
>>      which inject spurious /r characters. Adjust (\n|\r\n|\r) to 
>> (\r*\n+).
>>
>>      gcc/testsuite/ChangeLog:
>>
>>              * gfortran.dg/ISO_Fortran_binding_17.f90: As noted above.
> (...)This part will be integrated in the ChangeLog file, without the 
> preceding text.  Don't start with "As noted above", as there will be no 
> "above" to refer to.

Thank you, relearning how these things work with the automation scripts.

Jerry


  reply	other threads:[~2023-01-22 16:06 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 [this message]
2023-01-28  2:47     ` Jerry D
2023-01-28 16:44       ` Mikael Morin

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=9bac323a-89fe-5a0b-296b-57961b5f0d0d@gmail.com \
    --to=jvdelisle2@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvdelisle@protonmail.com \
    --cc=morin-mikael@orange.fr \
    /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).