From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 1/2] [gdb/testsuite] Fix copyright years in two files
Date: Tue, 28 Apr 2026 15:42:23 +0200 [thread overview]
Message-ID: <20260428134224.1406284-2-tdevries@suse.de> (raw)
In-Reply-To: <20260428134224.1406284-1-tdevries@suse.de>
I ran gdb/copyright.py, and encountered two files that were added in 2026 but
listed an older copyright year. Fix this.
---
gdb/testsuite/gdb.base/save-history.exp | 2 +-
gdb/testsuite/gdb.server/require-running.exp | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.base/save-history.exp b/gdb/testsuite/gdb.base/save-history.exp
index bb7a56b2a72..a24b0b9454c 100644
--- a/gdb/testsuite/gdb.base/save-history.exp
+++ b/gdb/testsuite/gdb.base/save-history.exp
@@ -1,4 +1,4 @@
-# Copyright 2023 Free Software Foundation, Inc.
+# Copyright 2026 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
diff --git a/gdb/testsuite/gdb.server/require-running.exp b/gdb/testsuite/gdb.server/require-running.exp
index 179c7ccc1ca..137c404697c 100644
--- a/gdb/testsuite/gdb.server/require-running.exp
+++ b/gdb/testsuite/gdb.server/require-running.exp
@@ -1,4 +1,4 @@
-# Copyright 2025 Free Software Foundation, Inc.
+# Copyright 2026 Free Software Foundation, Inc.
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
--
2.51.0
next prev parent reply other threads:[~2026-04-28 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 13:42 [PATCH 0/2] [gdb/testsuite] Fix some minor copyright issues Tom de Vries
2026-04-28 13:42 ` Tom de Vries [this message]
2026-04-28 13:42 ` [PATCH 2/2] [gdb/testsuite] Fix duplicate copyright notices Tom de Vries
2026-04-28 13:53 ` [PATCH 0/2] [gdb/testsuite] Fix some minor copyright issues Tom Tromey
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=20260428134224.1406284-2-tdevries@suse.de \
--to=tdevries@suse.de \
--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