From: Michael Tokarev <mjt@tls.msk.ru>
To: Anand J <anand.indukala@gmail.com>, qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, thuth@redhat.com, eblake@redhat.com
Subject: Re: [Qemu-trivial] [PATCH v4 0/2] Script changes to find duplicate #include entries
Date: Fri, 28 Oct 2016 17:32:20 +0300 [thread overview]
Message-ID: <d53da4ff-65f1-db59-4bd3-e4682fc8c44c@msgid.tls.msk.ru> (raw)
In-Reply-To: <1477033027-25315-1-git-send-email-anand.indukala@gmail.com>
21.10.2016 09:57, Anand J wrote:
> There were some files in the code base with multiple inclusion of the same header files.
> Following changes are made to mitigate this issue.
>
> 1) --check-dup-head option is added to the scripts/clean-includes to search files and
> find out such entries. This will help to catch redundant #includes in the future.
> 2) Removed most of the duplicate entries currently present in the code base using the
> script.
>
> Anand J (2):
> scripts/clean-includes: added duplicate #include check
> clean-up: removed duplicate #includes
Applied both to -trivial, thank you!
/mjt
prev parent reply other threads:[~2016-10-28 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 6:57 [Qemu-trivial] [Qemu-devel] [PATCH v4 0/2] Script changes to find duplicate #include entries Anand J
2016-10-21 6:57 ` [Qemu-trivial] [Qemu-devel] [PATCH v4 1/2] scripts/clean-includes: added duplicate #include check Anand J
2016-10-21 6:57 ` [Qemu-trivial] [Qemu-devel] [PATCH v4 2/2] clean-up: removed duplicate #includes Anand J
2016-10-24 9:06 ` [Qemu-trivial] [Qemu-devel] [PATCH v4 0/2] Script changes to find duplicate #include entries Anand J
2016-10-28 14:32 ` Michael Tokarev [this message]
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=d53da4ff-65f1-db59-4bd3-e4682fc8c44c@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=anand.indukala@gmail.com \
--cc=eblake@redhat.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).