From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PULL 0/3] SPDX checkpatch
Date: Fri, 28 Feb 2025 15:44:47 +0000 [thread overview]
Message-ID: <20250228154450.3185564-1-berrange@redhat.com> (raw)
The following changes since commit b69801dd6b1eb4d107f7c2f643adf0a4e3ec9124:
Merge tag 'for_upstream' of https://git.kernel.org/pub/scm/virt/kvm/mst/qemu into staging (2025-02-22 05:06:39 +0800)
are available in the Git repository at:
https://gitlab.com/berrange/qemu tags/spdx-check-pull-request
for you to fetch changes up to 6b7521818b26134726b3494cd06f04e30659ce2c:
scripts: forbid use of arbitrary SPDX tags besides license identifiers (2025-02-28 15:37:36 +0000)
----------------------------------------------------------------
* Mandate use of SPDX-License-Identifier in new files
* Validate SPDX license choices
* Forbid other SPDX tags
----------------------------------------------------------------
Daniel P. Berrangé (3):
scripts: mandate that new files have SPDX-License-Identifier
scripts: validate SPDX license choices
scripts: forbid use of arbitrary SPDX tags besides license identifiers
scripts/checkpatch.pl | 111 ++++++++++++++++++++++++++++++++++++++++++
1 file changed, 111 insertions(+)
--
2.48.1
next reply other threads:[~2025-02-28 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 15:44 Daniel P. Berrangé [this message]
2025-02-28 15:44 ` [PULL 1/3] scripts: mandate that new files have SPDX-License-Identifier Daniel P. Berrangé
2025-05-08 10:42 ` Peter Maydell
2025-05-12 13:52 ` Cédric Le Goater
2025-05-12 15:18 ` Cédric Le Goater
2025-05-12 15:28 ` Peter Maydell
2025-05-12 15:36 ` Cédric Le Goater
2025-02-28 15:44 ` [PULL 2/3] scripts: validate SPDX license choices Daniel P. Berrangé
2025-02-28 15:44 ` [PULL 3/3] scripts: forbid use of arbitrary SPDX tags besides license identifiers Daniel P. Berrangé
2025-03-03 12:12 ` [PULL 0/3] SPDX checkpatch Stefan Hajnoczi
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=20250228154450.3185564-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.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 NNTP newsgroup(s).