From: Eric Blake <eblake@redhat.com>
To: Anand J <anand.indukala@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH 1/2] script/clean-includes: added duplicate #include check
Date: Thu, 20 Oct 2016 08:48:53 -0500 [thread overview]
Message-ID: <e7cdd33b-15bd-e07d-760d-848fd73bb94e@redhat.com> (raw)
In-Reply-To: <1476957133-24382-1-git-send-email-anand.indukala@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
[meta-comment]
On 10/20/2016 04:52 AM, Anand J wrote:
> Added script to check duplicate #include entries. This check will scan
> and print the files in which duplicate #include entries are present.
This appears to be a v2 patch. But it is missing a 0/2 cover letter,
and mention of v2 in the subject line. 'git format-patch --cover-letter
-v2' will do what you want (as well as git send-email, which understands
all options accepted by format-patch); it's also possible to automate
git to send a cover letter any time you send more than one patch by
using 'git config format.coverLetter auto'.
More patch submission tips at http://wiki.qemu.org/Contribute/SubmitAPatch
>
> Script might output false positive entries as well. Such entries should
> not be removed. So if it finds any duplicate entries script will
> terminate with an exit status 1. Then each and every file should be
> checked manually and corrected if necessary.
>
> In order to enable the check use --check-duphead option with
> script/clean-includes.
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Anand J <anand.indukala@gmail.com>
> ---
> scripts/clean-includes | 50 +++++++++++++++++++++++++++++++++++++-------------
> 1 file changed, 37 insertions(+), 13 deletions(-)
>
--
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-10-20 13:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-20 9:52 [Qemu-devel] [PATCH 1/2] script/clean-includes: added duplicate #include check Anand J
2016-10-20 9:52 ` [Qemu-devel] [PATCH 2/2] clean-up: removed duplicate #includes Anand J
2016-10-20 13:48 ` Eric Blake [this message]
2016-10-20 13:57 ` [Qemu-devel] [PATCH 1/2] script/clean-includes: added duplicate #include check Eric Blake
-- strict thread matches above, loose matches on Subject: below --
2016-10-18 10:33 Anand J
2016-10-18 12:38 ` Anand J
2016-10-20 9:08 ` Thomas Huth
2016-10-20 9:56 ` Anand J
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=e7cdd33b-15bd-e07d-760d-848fd73bb94e@redhat.com \
--to=eblake@redhat.com \
--cc=anand.indukala@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=thuth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).