From: Greg KH <greg@kroah.com>
To: Charlemagne Lasse <charlemagnelasse@web.de>
Cc: linux-kernel@vger.kernel.org,
Charlemagne Lasse <charlemagnelasse@gmail.com>,
Jonas Oberg <jonas@fsfe.org>
Subject: Re: [RESENT,PATCH 0/5] licenses: Create LICENSES directory
Date: Mon, 13 Nov 2017 09:28:55 +0100 [thread overview]
Message-ID: <20171113082855.GA22719@kroah.com> (raw)
In-Reply-To: <20171112102729.17163-1-charlemagnelasse@outlook.com>
On Sun, Nov 12, 2017 at 12:23:43PM +0100, Charlemagne Lasse wrote:
> From: Charlemagne Lasse <charlemagnelasse@gmail.com>
>
> Hi,
>
> the FSFE created some best practices for the (re)distribution of open source
> software [1]. They partially talk about the the SPDX-License-Identifier tag
> which Greg Kroah-Hartman is already using to clarify the copyright status of
> some source files. But they also recommend to ship the complete license texts
> in a LICENSES directory when they are not already included in the source files.
<snip>
Nice, idea, we were wanting to do this as well, see this patch series
from Thomas that does much the same, but also helps explain the SPDX
tags we have been putting in the kernel source tree:
https://lkml.org/lkml/2017/11/12/110
thanks,
greg k-h
prev parent reply other threads:[~2017-11-13 8:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-12 11:23 [RESENT,PATCH 0/5] licenses: Create LICENSES directory Charlemagne Lasse
2017-11-12 11:13 ` [PATCH 2/5] licenses: Add verbatim LGPL-2.1 license text Charlemagne\ Lasse\
2017-11-12 11:13 ` [PATCH 3/5] licenses: Add verbatim MPL-1.1 " Charlemagne\ Lasse\
2017-11-12 11:13 ` [PATCH 4/5] licenses: Add verbatim GPL-1.0 " Charlemagne\ Lasse\
2017-11-12 11:13 ` [PATCH 5/5] licenses: Add verbatim GPL-2.0 " Charlemagne\ Lasse\
2017-11-12 11:23 ` [RESENT,PATCH 1/5] licenses: Add verbatim LGPL-2.0 " Charlemagne Lasse
2017-11-13 8:28 ` Greg KH [this message]
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=20171113082855.GA22719@kroah.com \
--to=greg@kroah.com \
--cc=charlemagnelasse@gmail.com \
--cc=charlemagnelasse@web.de \
--cc=jonas@fsfe.org \
--cc=linux-kernel@vger.kernel.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