From: Keith Seitz <keiths@redhat.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [RFC] [pre-commit] Add check-new-file-license
Date: Fri, 5 Jun 2026 11:06:18 -0700 [thread overview]
Message-ID: <74aa6f75-717f-4d94-90c4-acca98d165f5@redhat.com> (raw)
In-Reply-To: <20260605141051.881518-1-tdevries@suse.de>
Hi,
On 6/5/26 7:10 AM, Tom de Vries wrote:
> I forgot to add a copyright notice to a file.
>
> I came across gdb/contrib/license-check-new-files.sh, and ran it out of
> curiosity, and it pointed out the file.
>
> Add a pre-commit check check-new-file-license that runs the script.
Having dealt with licensing issues for Fedora/RHEL, I whole-
heartedly support this move. It's one less thing for all of us
downstream maintainers have to do.
[If accepted, you may also add my Reviewed-By.]
Thank you!
Keith
next prev parent reply other threads:[~2026-06-05 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 14:10 Tom de Vries
2026-06-05 18:06 ` Keith Seitz [this message]
2026-06-17 17:45 ` Tom Tromey
2026-06-17 19:19 ` Tom de Vries
2026-06-18 12:59 ` 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=74aa6f75-717f-4d94-90c4-acca98d165f5@redhat.com \
--to=keiths@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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