From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] checkpatch.pl: Add check for Change-Id
Date: Thu, 20 Mar 2014 03:08:20 -0700 [thread overview]
Message-ID: <1395310100.7776.3.camel@joe-AO722> (raw)
In-Reply-To: <1395255293-3419-1-git-send-email-cov@codeaurora.org>
On Wed, 2014-03-19 at 14:54 -0400, Christopher Covington wrote:
> A commit hook for the Gerrit code review server inserts change
> identifiers so Gerrit can track patches through multiple revisions.
> These identifiers are noise in the context of the upstream kernel.
> (Many Gerrit servers are private. Even given a public instance,
> given only a Change-Id, one must guess which server a change was
> tracked on. Patches submitted to the Linux kernel mailing lists
> should be able to stand on their own. If it's truly useful to
> reference code review on a Gerrit server, a URL is a much clearer
> way to do so.) Thus, issue an error when a Change-Id: line is
> encountered.
[]
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
[]
> @@ -1891,6 +1891,12 @@ sub process {
> }
> }
>
> +# Check for unwanted Gerrit info
> + if ($line =~ /^\s*change-id:/i) {
> + ERROR("BAD_SIGN_OFF",
> + "Remove Gerrit Change-Id's before submitting upstream.\n" . $herecurr);
> + }
> +
I think this needs an "$in_commit_log" test added
if ($in_commit_log &&
$line =~ /^\s*change-id:/i) {
And maybe use a separate "TYPE", not "BAD_SIGN_OFF".
Maybe "GERRIT_CHANGE_ID"
next prev parent reply other threads:[~2014-03-20 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 18:54 [PATCH] checkpatch.pl: Add check for Change-Id Christopher Covington
2014-03-20 10:08 ` Joe Perches [this message]
2014-03-21 17:24 ` Christopher Covington
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=1395310100.7776.3.camel@joe-AO722 \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.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).