linux-kernel - Re: [PATCH] checkpatch.pl: Check for the FSF mailing address

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131006134404.GB4706@kroah.com>
Date:	Sun, 6 Oct 2013 06:44:04 -0700
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Joe Perches <joe@...ches.com>,
	Josh Triplett <josh@...htriplett.org>,
	linux-kernel@...r.kernel.org, Andy Whitcroft <apw@...onical.com>
Subject: Re: [PATCH] checkpatch.pl: Check for the FSF mailing address

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?

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
shortend tags that can be used for it, and someone should be marking up
the whole kernel with them soon, which will be good.

Otherwise, it's up to the contributor, what they want to have in the
file.  But wrong addresses isn't ok, I'm sure we can all agree about
that.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/