From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] Reduce LICENCE/COPYING files
Date: Fri, 4 Jun 2021 11:48:53 +0200 [thread overview]
Message-ID: <YLn3BQHhZIq5vNId@pevik> (raw)
In-Reply-To: <CAEemH2dTBbHbh5Vf9EQyYMsvHKs3p4sZvoNyR=uCFM0X5siYtQ@mail.gmail.com>
Hi Li,
> > > > 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]:
> My perspective is to stay on the safe side, keep one in the LTP root
> dir and one in the subproject(e.g. open_posix).
This makes sense. I'll send RFC patch with your ack.
> The general files go with the SPDX identifier header.
+1
Kind regards,
Petr
next prev parent reply other threads:[~2021-06-04 9:48 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
2021-06-04 9:13 ` Li Wang
2021-06-04 9:21 ` Cyril Hrubis
2021-06-04 9:48 ` Petr Vorel [this message]
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=YLn3BQHhZIq5vNId@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