public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@adacore.com>
To: Paul Iannetta <piannetta@kalrayinc.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>,
	Thomas Schwinge <thomas@codesourcery.com>,
	gcc-patches@gcc.gnu.org, rdsandiford@googlemail.com
Subject: Re: [PATCH] Ignore case of header line in dg-extract-results.py
Date: Thu, 26 Oct 2023 01:09:01 -0300	[thread overview]
Message-ID: <orjzraja8y.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <20231024080416.k3htpcxgowjsgriv@ws2202.lin.mbt.kalray.eu> (Paul Iannetta's message of "Tue, 24 Oct 2023 10:04:16 +0200")

On Oct 24, 2023, Paul Iannetta <piannetta@kalrayinc.com> wrote:

> 	* dg-extract-results.py: Make the test_run regex case
> 	  insensitive.

It looks reasonable to me, but I'm not sure this is a change I'm
entitled to approve.  Thanks!

-- 
Alexandre Oliva, happy hacker            https://FSFLA.org/blogs/lxo/
   Free Software Activist                   GNU Toolchain Engineer
More tolerance and less prejudice are key for inclusion and diversity
Excluding neuro-others for not behaving ""normal"" is *not* inclusive

  reply	other threads:[~2023-10-26  4:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-14 14:24 [PATCH] Harmonize headers between both dg-extract-results scripts Paul Iannetta
2023-09-18  6:39 ` Paul Iannetta
2023-09-25  9:55   ` [PING] " Paul Iannetta
2023-09-26 14:29     ` Jeff Law
2023-09-29  8:19       ` Paul Iannetta
2023-09-29 14:52         ` Jeff Law
2023-10-18  9:35           ` Thomas Schwinge
2023-10-19 16:48             ` Jeff Law
2023-10-24  8:04               ` [PATCH] Ignore case of header line in dg-extract-results.py Paul Iannetta
2023-10-26  4:09                 ` Alexandre Oliva [this message]
2023-10-26  4:13                   ` Jeff Law

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=orjzraja8y.fsf@lxoliva.fsfla.org \
    --to=oliva@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeffreyalaw@gmail.com \
    --cc=piannetta@kalrayinc.com \
    --cc=rdsandiford@googlemail.com \
    --cc=thomas@codesourcery.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).