Re: [PATCH 00/10] treewide: add SPDX-License-Identifier headers
Daniel Gomez <[email protected]> Tue, 26 May 2026 13:03:59 +0200
| Newsgroups | dev.linux.lists.kdevops |
|---|---|
| Message-ID | <177979341107.63191.3419468896946318124.b4-ty@b4> |
From: Daniel Gomez <[email protected]> On Tue, 19 May 2026 15:34:21 +0200, Daniel Gomez wrote: > kdevops is licensed under copyleft-next-0.3.1 but the in-tree files > were missing SPDX-License-Identifier headers for the dominant content > categories. This series adds the headers consistently across shell > scripts, Python files, Makefiles, Kconfig files, Ansible role task > files, role defaults/handlers/vars/meta, top-level playbooks, .yaml > task files, and Rust/Go sources under workflows/rcloud. A final patch > fixes pre-existing malformed SPDX tags (missing colon, wrong spelling) > across 41 files to the canonical SPDX-License-Identifier: copyleft-next-0.3.1 > form. > > [...] Applied. [01/10] scripts: add SPDX-License-Identifier to shell scripts commit: dbd1ea5e196de1056a88115881321b94e299200a [02/10] scripts: add SPDX-License-Identifier to Python files commit: f2f04b7981dcd3d9fb0a8702887bd0101a2bd36f [03/10] make: add SPDX-License-Identifier to Makefiles commit: d68e24e0a5d7f2fb30475d25a0d7c9305a15e2ce [04/10] kconfigs: add SPDX-License-Identifier to Kconfig files commit: ca4065c0c8c8f5e441f1d529303cb8ea3052f8a0 [05/10] playbooks: add SPDX-License-Identifier to .yaml task files commit: 6f6611aabbe594bcad071e2d4b14fbe99ce8522b [06/10] playbooks: add SPDX-License-Identifier to role defaults/handlers/vars/meta commit: 89c7648d416a4f77310df80017848de46731786c [07/10] playbooks: add SPDX-License-Identifier to role task files commit: 6e4336af555636925fc899ea56e03160b61e0ada [08/10] playbooks: add SPDX-License-Identifier to top-level playbooks commit: 0faa8588b4e59471c56df06e5cfc7165a6b9d261 [09/10] treewide: fix SPDX-License-Identifier formatting commit: 35565d1b4935dc74f7faa5ee2000b699d3be7c8d [10/10] rcloud: add SPDX-License-Identifier to Rust and Go sources commit: 18984d61a26d1267e6e4093ac6fb9e191d6531ec Best regards, -- Daniel Gomez <[email protected]>