From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ul.coyote.org ([198.50.187.229]:54067 "EHLO ul.coyote.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934834AbdKPPPq (ORCPT ); Thu, 16 Nov 2017 10:15:46 -0500 Date: Thu, 16 Nov 2017 16:15:40 +0100 From: Jonas Oberg Subject: Re: [patch 1/7] Documentation: Add license-rules.rst to describe how to properly identify file licenses Message-ID: <20171116151540.GA18500@silk.coyote.org> References: <20171112191821.240484206@linutronix.de> <20171112192142.525567667@linutronix.de> <20171116080723.279591c8@lwn.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20171116080723.279591c8@lwn.net> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Jonathan Corbet Cc: Thomas Gleixner , LKML , Linus Torvalds , Andrew Morton , Philippe Ombredanne , Greg Kroah-Hartman , Christoph Hellwig , Russell King , Rob Herring , Joe Perches , linux-xfs@vger.kernel.org, Kate Stewart Hi, > One other thing that occurred to me is that documentation files, too, > are copyrightable and should have license identifiers. Would it make sense to take an incremental approach to this? Get the source code and identifiers worked on by Thomas et al through first, then think about and fix up potential other issues, like the top level COPYING file, or documentation :-) -- Jonas Öberg Executive Director FSFE e.V. - keeping the power of technology in your hands. Your support enables our work, please join us today http://fsfe.org/join