From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752118AbdKMI2t (ORCPT ); Mon, 13 Nov 2017 03:28:49 -0500 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:49983 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751836AbdKMI2s (ORCPT ); Mon, 13 Nov 2017 03:28:48 -0500 X-ME-Sender: Date: Mon, 13 Nov 2017 09:28:55 +0100 From: Greg KH To: Charlemagne Lasse Cc: linux-kernel@vger.kernel.org, Charlemagne Lasse , Jonas Oberg Subject: Re: [RESENT,PATCH 0/5] licenses: Create LICENSES directory Message-ID: <20171113082855.GA22719@kroah.com> References: <20171112102729.17163-1-charlemagnelasse@outlook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171112102729.17163-1-charlemagnelasse@outlook.com> User-Agent: Mutt/1.9.1 (2017-09-22) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Nov 12, 2017 at 12:23:43PM +0100, Charlemagne Lasse wrote: > From: Charlemagne Lasse > > 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. 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