Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/2] [gdb] Add missing copyright notice in pyproject.toml
Date: Thu, 26 Mar 2026 18:02:48 +0100	[thread overview]
Message-ID: <20260326170248.218742-3-tdevries@suse.de> (raw)
In-Reply-To: <20260326170248.218742-1-tdevries@suse.de>

I noticed gdb/pyproject.toml is missing a copyright notice.

Add this.  Since it was added in 2021, use copyright years 2021-2026.
---
 gdb/pyproject.toml | 16 ++++++++++++++++
 1 file changed, 16 insertions(+)

diff --git a/gdb/pyproject.toml b/gdb/pyproject.toml
index c8d1705ba15..8a62d29243b 100644
--- a/gdb/pyproject.toml
+++ b/gdb/pyproject.toml
@@ -1,3 +1,19 @@
+#!/bin/sh
+
+# Copyright (C) 2021-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
+# the Free Software Foundation; either version 3 of the License, or
+# (at your option) any later version.
+#
+# This program is distributed in the hope that it will be useful,
+# but WITHOUT ANY WARRANTY; without even the implied warranty of
+# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+# GNU General Public License for more details.
+#
+# You should have received a copy of the GNU General Public License
+# along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
 [tool.black]
 include = "\\.py(\\.in)?$"
 
-- 
2.51.0


  parent reply	other threads:[~2026-03-26 17:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-26 17:02 [PATCH 0/2] [gdb] Add missing copyright notices Tom de Vries
2026-03-26 17:02 ` [PATCH 1/2] [gdb/contrib] " Tom de Vries
2026-04-10 12:30   ` [PING][PATCH " Tom de Vries
2026-06-01 12:54     ` Tom de Vries
2026-03-26 17:02 ` Tom de Vries [this message]
2026-04-10 12:29   ` [PATCH 2/2] [gdb] Add missing copyright notice in pyproject.toml Tom de Vries

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=20260326170248.218742-3-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