From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: 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 00:05:57 -0700 [thread overview]
Message-ID: <20131006070557.GA1679@kroah.com> (raw)
In-Reply-To: <1381042912.2081.146.camel@joe-AO722>
On Sun, Oct 06, 2013 at 12:01:52AM -0700, Joe Perches wrote:
> On Sat, 2013-10-05 at 23:27 -0700, Greg Kroah-Hartman wrote:
> > On Sat, Oct 05, 2013 at 11:51:48AM -0700, Joe Perches wrote:
> > > On Sat, 2013-10-05 at 11:43 -0700, Josh Triplett wrote:
> > > > Kernel maintainers reject new instances of the GPL boilerplate paragraph
> > > > directing people to write to the FSF for a copy of the GPL, since the
> > > > FSF has moved in the past and may do so again.
> > > []
> > > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > > []
> > > > +# Check for FSF mailing addresses.
> > > > + if ($rawline =~ /You should have received a copy/ ||
> > > There are over 9,000 of these in the tree.
> > > > + $rawline =~ /write to the Free Software/ ||
> > > Over 7,000
> > > > + $rawline =~ /59 Temple Place/ ||
> > > Over 3,500
> > > > + $rawline =~ /51 Franklin Street/) {
> > > Over 1,500
> >
> > Then we should remove them all.
> []
> > I don't want to see this get worse over time, Josh, thanks for doing
> > this checkpatch patch.
>
> What about the warranty disclaimer?
>
> This program is distributed in the hope that it will be useful,
> but WITHOUT ANY WARRANTY; without even the implied warranty of
> MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> GNU General Public License for more details.
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...
thanks,
greg k-h
next prev parent reply other threads:[~2013-10-06 7:22 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 [this message]
2013-10-06 8:10 ` Borislav Petkov
2013-10-06 13:44 ` Greg Kroah-Hartman
2013-10-06 13:55 ` Borislav Petkov
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=20131006070557.GA1679@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=apw@canonical.com \
--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).