From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Michael Stefaniuc <mstefani@redhat.com>
Cc: Kamil Dudka <kdudka@redhat.com>, sparse <linux-sparse@vger.kernel.org>
Subject: Re: Detect unused header files?
Date: Thu, 6 Aug 2009 10:09:55 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.0908061007240.10398@localhost> (raw)
In-Reply-To: <4A7ADA01.6020402@redhat.com>
On Thu, 6 Aug 2009, Michael Stefaniuc wrote:
> Kamil Dudka wrote:
> > On Thu August 6 2009 14:16:45 Kamil Dudka wrote:
> >>> has anyone tried cscout?
> >>>
> >>> http://www.spinellis.gr/cscout/
> >> The homepage looks interesting, but where can I download its sources?
> >
> > FYI we figured out with rday off-list that there are no sources available.
> >
> > Please leave a note here if you find them.
> It is a proprietary application that is free as in beer to use for
> checking open source code. But careful as the application phones
> home (see the FAQ). I wanted to use it too on Wine but that stopped
> me.
while i understand the dislike OSS folks have for that sort of
thing, is there anything fundamentally harmful with what cscout would
be "sending home" WRT the linux kernel source tree? i'm not arguing
one way or the other -- i'm just wondering if the benefits of running
cscout on the kernel would outweigh the annoyance of how it behaves.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca
Twitter: http://twitter.com/rpjday
"Kernel Newbie Corner" column @ linux.com: http://cli.gs/WG6WYX
========================================================================
next prev parent reply other threads:[~2009-08-06 14:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-28 18:18 Detect unused header files? Sam Ravnborg
2009-07-28 20:36 ` Christopher Li
2009-07-28 20:36 ` Robert P. J. Day
2009-07-28 20:49 ` Christopher Li
2009-07-28 21:04 ` Sam Ravnborg
2009-07-28 21:38 ` Christopher Li
2009-07-30 10:55 ` Christopher Li
2009-07-30 11:12 ` Derek M Jones
2009-07-30 20:36 ` Sam Ravnborg
2009-08-04 21:49 ` Christopher Li
2009-08-05 6:12 ` Sam Ravnborg
2009-08-06 11:14 ` Marko Kreen
2009-08-06 11:17 ` Robert P. J. Day
2009-08-06 12:16 ` Kamil Dudka
2009-08-06 12:15 ` Robert P. J. Day
2009-08-06 13:01 ` Kamil Dudka
2009-08-06 13:26 ` Michael Stefaniuc
2009-08-06 14:09 ` Robert P. J. Day [this message]
2009-08-06 17:39 ` Christopher Li
2009-07-28 20:58 ` Sam Ravnborg
2009-07-28 21:21 ` Christopher Li
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=alpine.LFD.2.00.0908061007240.10398@localhost \
--to=rpjday@crashcourse.ca \
--cc=kdudka@redhat.com \
--cc=linux-sparse@vger.kernel.org \
--cc=mstefani@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).