public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] Reduce LICENCE/COPYING files
Date: Thu, 3 Jun 2021 13:57:17 +0200	[thread overview]
Message-ID: <YLjDnXeWib2KSILF@pevik> (raw)
In-Reply-To: <YLi3XqA3hLh7HWqn@yuki>

Hi Cyril,

> Hi!
> > I suppose it's safe to keep only single licence in testcases/open_posix_testsuite/,
> > but could we keep only COPYING in the root directory and delete the rest?
> > Or keep COPYING and testcases/open_posix_testsuite/COPYING only?

> Do we even need these files? Isn't SPDX identifier enough these days?
It be nice we don't need it, but not sure. Looking into kernel tree, there is
LICENSES folder [1] and they describe how they use SPDX [2]:

Valid-License-Identifier: GPL-2.0
Valid-License-Identifier: GPL-2.0-only
Valid-License-Identifier: GPL-2.0+
Valid-License-Identifier: GPL-2.0-or-later
SPDX-URL: https://spdx.org/licenses/GPL-2.0.html
Usage-Guide:
  To use this license in source code, put one of the following SPDX
  tag/value pairs into a comment according to the placement
  guidelines in the licensing rules documentation.
  For 'GNU General Public License (GPL) version 2 only' use:
    SPDX-License-Identifier: GPL-2.0
  or
    SPDX-License-Identifier: GPL-2.0-only
  For 'GNU General Public License (GPL) version 2 or any later version' use:
    SPDX-License-Identifier: GPL-2.0+
  or
    SPDX-License-Identifier: GPL-2.0-or-later
License-Text:

		    GNU GENERAL PUBLIC LICENSE
		       Version 2, June 1991
...

Kind regards,
Petr

[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/LICENSES
[2] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/LICENSES/preferred/GPL-2.0

  reply	other threads:[~2021-06-03 11:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 13:00 [LTP] [RFC] Reduce LICENCE/COPYING files Petr Vorel
2021-06-03 11:05 ` Cyril Hrubis
2021-06-03 11:57   ` Petr Vorel [this message]
2021-06-04  9:13     ` Li Wang
2021-06-04  9:21       ` Cyril Hrubis
2021-06-04  9:48       ` Petr Vorel
2021-06-04 17:47         ` Enji Cooper
2021-06-04 18:15           ` Cyril Hrubis
2021-06-07  8:14             ` Petr Vorel

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=YLjDnXeWib2KSILF@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /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