linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Joe Perches <joe@perches.com>,
	Josh Triplett <josh@joshtriplett.org>,
	linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>
Subject: Re: [PATCH] checkpatch.pl: Check for the FSF mailing address
Date: Sun, 6 Oct 2013 15:55:07 +0200	[thread overview]
Message-ID: <20131006135507.GA18082@pd.tnic> (raw)
In-Reply-To: <20131006134404.GB4706@kroah.com>

On Sun, Oct 06, 2013 at 06:44:04AM -0700, Greg Kroah-Hartman wrote:
> On Sun, Oct 06, 2013 at 10:10:33AM +0200, Borislav Petkov wrote:
> > On Sun, Oct 06, 2013 at 12:05:57AM -0700, Greg Kroah-Hartman wrote:
> > > As an individual file is not the sum of the "program", I would argue
> > > that it is not needed, but some companies like to feel better by
> > > adding it. So I really don't mind either way, as it would involve
> > > arguing with lawyers about this type of thing, and I do enough of that
> > > already that I don't go out of my way to do it more...
> > 
> > What about a short sentence pointing at 'COPYING' instead?
> 
> Why?  What would that do?

Save us the short one or two lines "this file is ..."

> Listen, all we really need is a short one or two line "this file is
> released under the FOO license" in the file.  The SPDX project has the

All I'm suggesting is that it might be even simpler to add

"See COPYING in the kernel source repository for the license of this file."

or a similar text as COPYING contains the full text of the license.
Basically a pointer to it.

This has the added advantage to your short line that it points to the
exact license text and lawyers are happy.

<snip stuff we agree about anyway>

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-10-06 13:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-05 18:43 [PATCH] checkpatch.pl: Check for the FSF mailing address Josh Triplett
2013-10-05 18:51 ` Joe Perches
2013-10-05 19:03   ` Josh Triplett
2013-10-06  6:27   ` Greg Kroah-Hartman
2013-10-06  7:01     ` Joe Perches
2013-10-06  7:05       ` Greg Kroah-Hartman
2013-10-06  8:10         ` Borislav Petkov
2013-10-06 13:44           ` Greg Kroah-Hartman
2013-10-06 13:55             ` Borislav Petkov [this message]
2013-10-06 19:18               ` Greg Kroah-Hartman
2013-10-06 20:07                 ` Borislav Petkov
2013-10-06 19:19       ` Rob Landley
2013-10-06 21:16       ` Josh Triplett
2013-10-06 21:18     ` Josh Triplett
2013-10-06 21:27       ` Joe Perches
2013-10-06 21:33         ` Josh Triplett
2013-10-06 21:48           ` Joe Perches
2013-10-06 22:23             ` [PATCHv2] " Josh Triplett
2013-10-06 23:05               ` Greg Kroah-Hartman
2013-10-06 23:16               ` Joe Perches

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=20131006135507.GA18082@pd.tnic \
    --to=bp@alien8.de \
    --cc=apw@canonical.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=josh@joshtriplett.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;
as well as URLs for NNTP newsgroup(s).