From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Colin Lord <clord@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] checkpatch: consider git extended headers valid patches
Date: Fri, 15 Jul 2016 11:52:21 -0600 [thread overview]
Message-ID: <578922D5.9010003@redhat.com> (raw)
In-Reply-To: <1468576014-28788-1-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On 07/15/2016 03:46 AM, Stefan Hajnoczi wrote:
> 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>
> ---
> scripts/checkpatch.pl | 5 +++++
> 1 file changed, 5 insertions(+)
Reviewed-by: Eric Blake <eblake@redhat.com>
and especially nice since we recommend diff.renames = true in our patch
submission guidelines.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-07-15 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 9:46 [Qemu-devel] [PATCH] checkpatch: consider git extended headers valid patches Stefan Hajnoczi
2016-07-15 17:52 ` Eric Blake [this message]
2016-07-18 12:15 ` Stefan Hajnoczi
2016-07-18 13:15 ` Paolo Bonzini
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=578922D5.9010003@redhat.com \
--to=eblake@redhat.com \
--cc=clord@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.