From: Josh Triplett <josh@joshtriplett.org>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] checkpatch.pl: Check for the FSF mailing address
Date: Sat, 5 Oct 2013 12:03:25 -0700 [thread overview]
Message-ID: <20131005190325.GS5771@leaf> (raw)
In-Reply-To: <1380999108.2081.138.camel@joe-AO722>
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
> []
> > @@ -1859,6 +1859,16 @@ sub process {
> > $rpt_cleaners = 1;
> > }
> >
> > +# 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
And there shouldn't be any more added. (Also, case in point, note that
the FSF is no longer at "59 Temple Place".)
> > + my $herevet = "$here\n" . cat_vet($rawline) . "\n";
> > + ERROR("FSF_MAILING_ADDRESS",
> > + "Do not include the paragraph about writing to the Free Software Foundation's mailing address from the sample GPL notice. The FSF has changed addresses in the past, and may do so again. Linux already includes a copy of the GPL.\n" . $herevet)
>
> Is this really a useful ERROR condition?
> Maybe a CHK --strict test or a warning instead?
How about making it a hard ERROR in patch mode, making "59 Temple Place"
an error in any mode, and making the other lines only warnings in file
mode?
Note that I made it an error because for many maintainers it's an
automatic patch rejection.
- Josh Triplett
next prev parent reply other threads:[~2013-10-05 19:03 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 [this message]
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
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=20131005190325.GS5771@leaf \
--to=josh@joshtriplett.org \
--cc=apw@canonical.com \
--cc=gregkh@linuxfoundation.org \
--cc=joe@perches.com \
--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