Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Andrea Pinski <andrew.pinski@oss.qualcomm.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/1] dg-extract-results.{sh, py}: Optionally read file list from stdin/file
Date: Fri, 4 Sep 2026 13:18:31 +0100	[thread overview]
Message-ID: <5b6035d0-ef9a-4aaa-bd29-61e1756eba95@palves.net> (raw)
In-Reply-To: <CALvbMcB2ssG3TWpCtOs+9950gyhbhFH+jEE+uXqj9RMv7CyNQQ@mail.gmail.com>

On 2026-09-04 04:08, Andrea Pinski wrote:

>> contrib/ChangeLog:
>>
>>         * dg-extract-results.py: Handle new "-f list-file" option.
>>         * dg-extract-results.sh: Ditto.
> 
> Ok.

Thank you!  I've pushed it to both repos.

> 
>>
>> Change-Id: Iaced5ba228972ce267f355de65fe5ad8a1e38c68
> 
> Note we normally don't have Change-Id in the commit message; I know it
> is from gerrit so please remove it before pushing the patch.

I did that.

For the binutils-gdb side, I pushed this follow up patch below, too.

--- 
contrib: sync dg-extract-results.{sh,py} with GCC

The previous commit already brought in the code changes, but we're
still missing a copyright year update in dg-extract-results.sh, which
this now brings in.

Record that both files are synced now in the ChangeLog.

---
 contrib/ChangeLog             | 5 +++++
 contrib/dg-extract-results.sh | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/contrib/ChangeLog b/contrib/ChangeLog
index 8c0a4971fd2..da24bcab232 100644
--- a/contrib/ChangeLog
+++ b/contrib/ChangeLog
@@ -1,3 +1,8 @@
+2026-09-04  Pedro Alves  <pedro@palves.net>
+
+	* dg-extract-results.py: Sync with GCC.
+	* dg-extract-results.sh: Sync with GCC.
+
 2026-05-29  Kevin Buettner  <kevinb@redhat.com>
 
 	* dg-extract-results.py: Sync with GCC.
diff --git a/contrib/dg-extract-results.sh b/contrib/dg-extract-results.sh
index d03e1a9b4e1..f3093f94582 100755
--- a/contrib/dg-extract-results.sh
+++ b/contrib/dg-extract-results.sh
@@ -6,7 +6,7 @@
 # The resulting file can be used with test result comparison scripts for
 # results from tests that were run in parallel.  See usage() below.
 
-# Copyright (C) 2008-2025 Free Software Foundation, Inc.
+# Copyright (C) 2008-2026 Free Software Foundation, Inc.
 # Contributed by Janis Johnson <janis187@us.ibm.com>
 #
 # This file is part of GCC.

base-commit: 2e328496db8d224a697d50621563e980cf1d301a
-- 
2.54.0



      reply	other threads:[~2026-09-04 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-03 18:55 [PATCH 0/1] " Pedro Alves
2026-09-03 18:55 ` [PATCH 1/1] " Pedro Alves
2026-09-04  3:08   ` Andrea Pinski
2026-09-04 12:18     ` Pedro Alves [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=5b6035d0-ef9a-4aaa-bd29-61e1756eba95@palves.net \
    --to=pedro@palves.net \
    --cc=andrew.pinski@oss.qualcomm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    /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