public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Kepplinger <martink@posteo.de>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: akpm@linux-foundation.org, corbet@lwn.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] samples: replace FSF address with web source in license notices
Date: Wed, 15 Nov 2017 08:46:51 +0100	[thread overview]
Message-ID: <19e33c22c64218d4fca53871f3408871@posteo.de> (raw)
In-Reply-To: <20171115062955.GA16601@kroah.com>

Am 15.11.2017 07:29 schrieb Greg KH:
> On Tue, Nov 14, 2017 at 10:50:37AM +0100, Martin Kepplinger wrote:
>> A few years ago the FSF moved and "59 Temple Place" is wrong. Having 
>> this
>> still in our source files feels old and unmaintained.
>> 
>> Let's take the license statement serious and not confuse users.
>> 
>> As https://www.gnu.org/licenses/gpl-howto.html suggests, we replace 
>> the
>> postal address with "<http://www.gnu.org/licenses/>" in the samples
>> directory.
> 
> What would be best is to just put the SPDX single line at the top of 
> the
> files, and then remove this license "boilerplate" entirely.  I've
> started to do that with some subsystems already (drivers/usb/ and
> drivers/tty/ are almost finished, see Linus's tree for details), and
> I've sent out a patch series for drivers/s390/ yesterday if you want to
> see an example of how to do it.
> 
> Could you do that here instead of this patch as well?
> 

Is there consensus about this? I'm not a layer, but is this clear enough 
for
useres? And what holds against only adding the new SPDX tag line at the 
top?

Other than I don't like mixing // and /**/ comments, it indeed looks
quite clean. Is there consensus about the syntax too?

thanks

                                martin

  reply	other threads:[~2017-11-15  7:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14  9:50 [PATCH] samples: replace FSF address with web source in license notices Martin Kepplinger
2017-11-15  6:29 ` Greg KH
2017-11-15  7:46   ` Martin Kepplinger [this message]
2017-11-15  8:45     ` Greg KH
2017-11-15 20:44       ` [PATCH] samples: replace outdated permission statement with SPDX identifiers Martin Kepplinger
2017-11-16 11:41         ` Greg KH
2017-11-17 22:53           ` Jonathan Corbet
2017-11-17 23:43             ` Martin Kepplinger
2017-11-18  0:13               ` Jonathan Corbet
2017-11-18  8:33                 ` Martin Kepplinger
2017-11-18 10:20               ` Greg KH
2017-11-18 10:17             ` Greg KH
2017-11-18 11:21               ` Martin Kepplinger
2017-11-16 13:56         ` Philippe Ombredanne
2017-11-22 22:23       ` [PATCH] samples: replace FSF address with web source in license notices Pavel Machek

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=19e33c22c64218d4fca53871f3408871@posteo.de \
    --to=martink@posteo.de \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.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