linux-master/scripts/checkpatch.pl

95   -g, --git                  treat FILE as a single commit or git revision range
96                              single git commit with:
1228 	my ($commit, $id, $desc) = @_;
1232 	my $output = `${git_command} log --no-color --format='%H %s' -1 $commit 2>&1`;
1238 	if ($lines[0] =~ /^error: short SHA1 $commit is ambiguous/) {
1240 # all matching commit ids, but it's very slow...
1246 #		    echo "commit $(cut -c 1-12,41-)"
1248 	} elsif ($lines[0] =~ /^fatal: ambiguous argument '$commit': unknown revision or path not in the working tree\./ ||
1249 		 $lines[0] =~ /^fatal: bad object $commit/) {
1268 # If input is git commits, extract all commits from the commit expressions.
2648 	my $commit_log_lines = 0;	#Number of commit log lines
2922 # Verify the existence of a commit log if appropriate
2930 			     "Missing commit description - Add an appropriate one\n");
2934 # Check if the commit log has what seems like a diff which can confuse patch
2941 			      "Avoid using diff content in the commit message - patch(1) might not work\n" . $herecurr);
3195 		    $line =~ /^\s*fixes:?\s*(?:commit\s*)?[0-9a-f]{5,}\b/i) {
3198 			my $title = "commit title";
3253 # Check if the commit log is in a possible stack dump
3265 # Check for line lengths > 75 in commit log, warn once
3276 			     "Prefer a maximum 75 chars per line (possible unwrapped commit description?)\n" . $herecurr);
3318 # Check for git id commit length and improperly formed commit descriptions
3319 # A correctly formed commit description is:
3320 #    commit <SHA-1 hash length 12+ chars> ("Complete commit subject")
3321 # with the commit subject '("' prefix and '")' suffix
3325 # A commit match can span multiple lines so this block attempts to find a
3326 # complete typical commit on a maximum of 3 lines
3329 		    $line !~ /^\s*(?:Link|Patchwork|http|https|BugLink|base-commit):/i &&
3330 		    $line !~ /^This reverts commit [0-9a-f]{7,40}/ &&
3343 			my $orig_desc = "commit description";
3388 				      "Please use git commit description style 'commit <12+ chars of sha1> (\"<title line>\")' - ie: '${init_char}ommit $id (\"$description\")'\n" . $herectx);
3390 			#don't report the next line if this line ends in commit and the sha1 hash is the next line
3437 			    "Invalid UTF-8, patch and commit message should be encoded in UTF-8\n" . $hereptr);
3440 # Check if it's the start of a commit log
3444 		      $rawline =~ /^(?:commit\b|from\b|[\w-]+:)/i)) {
3450 # Check if there is UTF-8 in a commit log when a mail header has explicitly
3461 			    "8-bit UTF-8 used in possible commit log\n" . $herecurr);
3464 # Check for absolute kernel paths in commit message
3499 # check for invalid commit id
3506 				     "Unknown commit id '$2', maybe rebased or not pulled?\n" . $herecurr);
7664 				     "Prefer \"GPL\" over \"GPL v2\" - see commit bf7fbeeae6db (\"module: Cure the MODULE_LICENSE \"GPL\" vs. \"GPL v2\" bogosity\")\n" . $herecurr) &&