diff options
| author | Stefan Hajnoczi <stefanha@redhat.com> | 2016-07-15 10:46:54 +0100 |
|---|---|---|
| committer | Stefan Hajnoczi <stefanha@redhat.com> | 2016-07-18 15:10:52 +0100 |
| commit | f8dccbb63463d72dcf273b583d41810a01feab26 (patch) | |
| tree | e81decfd1df0186f12a70f83dd590b7919e06d3c /target-s390x/trace-events | |
| parent | 7e00346505feb94ee740d311621eb0bf4c14d6db (diff) | |
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>
Diffstat (limited to 'target-s390x/trace-events')
0 files changed, 0 insertions, 0 deletions