From: "Marco Costalba" <mcostalba@gmail.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: linux-kernel@vger.kernel.org
Subject: Re: List of possible duplicated include files in include/
Date: Sun, 4 Nov 2007 19:52:31 +0100 [thread overview]
Message-ID: <e5bfff550711041052m1c55571bx49c60dd6ce407d01@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711041347001.12818@localhost.localdomain>
On 11/4/07, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Sun, 4 Nov 2007, Marco Costalba wrote:
>
> > Here the number of false positives is overhelming, but perhaps there
> > are also _real_ duplicated include somewhere in the bunch:
> >
> > include/acpi/acpi_bus.h:
> > #include <linux/device.h>
>
> ... snip header file output ...
>
> i deliberately left out header files from my script output. i can
> tweak the script and add this to the web page as well.
>
Here the real job is to fliter out false positives more then print out
the list I would say ;-)
Marco
next prev parent reply other threads:[~2007-11-04 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 18:44 Marco Costalba
2007-11-04 18:48 ` Robert P. J. Day
2007-11-04 18:52 ` Marco Costalba [this message]
2007-11-04 19:01 ` Robert P. J. Day
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=e5bfff550711041052m1c55571bx49c60dd6ce407d01@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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
all inboxes | Powered by JetHome®