From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>
Subject: [PATCH 4/6] gdb/copyright.py: Add update-netbsd.sh to MULTIPLE_COPYRIGHT_HEADERS
Date: Sat, 1 Jan 2022 19:12:48 +0400 [thread overview]
Message-ID: <20220101151250.35116-5-brobecker@adacore.com> (raw)
In-Reply-To: <20220101151250.35116-1-brobecker@adacore.com>
Add gdb/syscalls/update-netbsd.sh to the reminder printed
at the end of the execution listing all the files where
a manual update of the copyright header is needed. This
scripts contains some inline code which includes a copyright
header.
---
gdb/copyright.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/gdb/copyright.py b/gdb/copyright.py
index 560754f4983..c4e6f947fe4 100644
--- a/gdb/copyright.py
+++ b/gdb/copyright.py
@@ -245,6 +245,7 @@ MULTIPLE_COPYRIGHT_HEADERS = (
"gdb/doc/gdb.texinfo",
"gdb/doc/refcard.tex",
"gdb/gdbarch.sh",
+ "gdb/syscalls/update-netbsd.sh",
)
# The list of file which have a copyright, but not head by the FSF.
--
2.32.0
next prev parent reply other threads:[~2022-01-01 15:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 15:12 [FYI] GDB Start of New Year Procedure Joel Brobecker
2022-01-01 15:12 ` [PATCH 1/6] Update Copyright Year in gdb, gdbserver and gdbreplay version output Joel Brobecker
2022-01-01 15:12 ` [PATCH 3/6] Manual copyright year update of various GDB files Joel Brobecker
2022-01-10 5:10 ` Daniel Black
2022-01-10 5:37 ` Joel Brobecker
2022-01-10 6:47 ` Daniel Black
2022-01-10 17:29 ` Eli Zaretskii
2022-01-01 15:12 ` Joel Brobecker [this message]
2022-01-01 15:12 ` [PATCH 5/6] Fix copyright header in gdb/testsuite/gdb.arch/powerpc-power10.exp Joel Brobecker
2022-01-01 15:12 ` [PATCH 6/6] Update Copyright year " Joel Brobecker
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=20220101151250.35116-5-brobecker@adacore.com \
--to=brobecker@adacore.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).