checkpatch: consider git extended headers valid patches
commitf8dccbb63463d72dcf273b583d41810a01feab26
authorStefan Hajnoczi <stefanha@redhat.com>
Fri, 15 Jul 2016 09:46:54 +0000 (15 10:46 +0100)
committerStefan Hajnoczi <stefanha@redhat.com>
Mon, 18 Jul 2016 14:10:52 +0000 (18 15:10 +0100)
treee81decfd1df0186f12a70f83dd590b7919e06d3c
parent7e00346505feb94ee740d311621eb0bf4c14d6db
checkpatch: consider git extended headers valid patches

Renames look like this with git-diff(1) when diff.renames = true is set:

  diff --git a/a b/b
  similarity index 100%
  rename from a
  rename to b

This raises the "Does not appear to be a unified-diff format patch"
error because checkpatch.pl only considers a diff valid if it contains
at least one "@@" hunk.

This patch accepts renames and copies too so that checkpatch.pl exits
successfully when a diff only renames/copies files.  The git diff
extended header format is described on the git-diff(1) man page.

Reported-by: Colin Lord <clord@redhat.com>
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Message-id: 1468576014-28788-1-git-send-email-stefanha@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
scripts/checkpatch.pl