From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>,
Julien Grall <julien@xen.org>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags
Date: Fri, 5 May 2023 15:13:49 +0200 [thread overview]
Message-ID: <40d70f11-37e7-ff29-37c1-a94d3e286455@suse.com> (raw)
In-Reply-To: <20230505130533.3580545-3-andrew.cooper3@citrix.com>
On 05.05.2023 15:05, Andrew Cooper wrote:
> The SPDX forms without an explicit -only or -or-later suffix are deprecated
> and should not be used.
I guess this wants a reference to where this is specified. In particular ...
> --- a/LICENSES/LGPL-2.1
> +++ b/LICENSES/LGPL-2.1
> @@ -1,5 +1,5 @@
> -Valid-License-Identifier: LGPL-2.1
> -Valid-License-Identifier: LGPL-2.1+
> +Valid-License-Identifier: LGPL-2.1-only
> +Valid-License-Identifier: LGPL-2.1-or-later
>
> SPDX-URL: https://spdx.org/licenses/LGPL-2.1.html
... I can't spot anything like this under e.g. this URL.
Also is there a reason you add Deprecated-Identifier: only to GPL-2.0?
Enumerating them would seem reasonable to me, not just for completeness,
but also in case we end up importing a file with a deprecated tag.
Jan
next prev parent reply other threads:[~2023-05-05 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 13:05 [PATCH 0/2] LICENSES improvements/corrections Andrew Cooper
2023-05-05 13:05 ` [PATCH 1/2] LICENSES: Improve the legibility of these files Andrew Cooper
2023-05-05 13:06 ` Jan Beulich
2023-05-05 22:29 ` Stefano Stabellini
2023-05-05 13:05 ` [PATCH 2/2] LICENSES: Remove the use of deprecated LGPL SPDX tags Andrew Cooper
2023-05-05 13:13 ` Jan Beulich [this message]
2023-05-05 13:22 ` Andrew Cooper
2023-05-05 13:31 ` Jan Beulich
2023-05-05 13:36 ` Andrew Cooper
2023-05-05 15:30 ` Anthony PERARD
2023-05-05 15:52 ` Andrew Cooper
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=40d70f11-37e7-ff29-37c1-a94d3e286455@suse.com \
--to=jbeulich@suse.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.