From: NightStrike <nightstrike@gmail.com>
To: Jerry D <jvdelisle2@gmail.com>
Cc: Jerry DeLisle <jvdelisle@protonmail.com>,
gfortran <fortran@gcc.gnu.org>,
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 00:28:14 -0500 [thread overview]
Message-ID: <CAF1jjLtDicemaG4U4_+uQsF+6Gyx2S9u1NgGWv-WdPtmhoK8yQ@mail.gmail.com> (raw)
In-Reply-To: <c876c113-da4c-a70f-172f-0824018bf8ea@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 479 bytes --]
On Sat, Jan 21, 2023, 18:59 Jerry D via Fortran <fortran@gcc.gnu.org> wrote:
>
> 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+).
>
Just to be clear, all simulators inject the spurious r's. I replicated the
problem on Linux.
next prev parent reply other threads:[~2023-01-22 5:28 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 [this message]
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
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=CAF1jjLtDicemaG4U4_+uQsF+6Gyx2S9u1NgGWv-WdPtmhoK8yQ@mail.gmail.com \
--to=nightstrike@gmail.com \
--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).