checkpatch: consider git extended headers valid patches
commitd211bd6016a5d2d59911c6d3d343f114e9853366
authorStefan Hajnoczi <stefanha@redhat.com>
Fri, 15 Jul 2016 09:46:54 +0000 (15 10:46 +0100)
committerPaolo Bonzini <pbonzini@redhat.com>
Sun, 17 Jul 2016 07:59:21 +0000 (17 09:59 +0200)
tree86170c5edb35cd77d13027f20b4ce78d972d69ab
parent8cc46787b5b58f01a11c919c7ff939ed009e27fc
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>
Message-Id: <1468576014-28788-1-git-send-email-stefanha@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
scripts/checkpatch.pl