From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
Gilles.Muller@lip6.fr, nicolas.palix@imag.fr, mmarek@suse.com,
linux-kernel@vger.kernel.org, cocci@systeme.lip6.fr
Subject: Re: [Cocci] [PATCH v3 3/6] scripts: add glimpse.sh for indexing the kernel
Date: Wed, 15 Jun 2016 20:00:00 +0200 [thread overview]
Message-ID: <20160615180000.GW11948@wotan.suse.de> (raw)
In-Reply-To: <trinity-8eae95d7-f827-44c4-b4d3-123561a053f8-1465986379121@3capp-webde-bap31>
On Wed, Jun 15, 2016 at 12:26:19PM +0200, SF Markus Elfring wrote:
> > Glimpse is a tool you can use to index the kernel.
> > The tool was recently open sourced under the ISC license
> > and can be obtained at:
>
> Do you find any official announcement for this software evolution?
I had reached out to Udi Manber in 2014, with the help of a few others we
helped persuade University of Arizona of an ISC release.
http://webglimpse.net/
Its vaguely mentioned there. That's as good as it gets...
> Is the wording "recent" really appropriate if you would eventually like to refer to a repository which was published in the year 2014?
> https://github.com/gvelez17/glimpse/
Sadly the original release didn't compile, I reported the issue in hopes it would
be fixed. Nothing has happened since and I got tired of waiting so I forked
and fixed it myself. I sent a pull request but I don't think its been merged
yet.
Luis
next prev parent reply other threads:[~2016-06-15 18:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 20:05 [PATCH v2 0/5] coccicheck: extend with parmap and indexing heuristics Luis R. Rodriguez
2016-06-14 20:05 ` [PATCH v2 1/5] coccicheck: enable parmap support Luis R. Rodriguez
2016-06-14 20:05 ` [PATCH v2 2/5] scripts: add glimpse.sh for indexing the kernel Luis R. Rodriguez
2016-06-14 20:05 ` [PATCH v2 3/5] coccicheck: add indexing enhancement options Luis R. Rodriguez
2016-06-14 20:05 ` [PATCH v2 4/5] coccicheck: document how to pass extra options to coccinelle Luis R. Rodriguez
2016-06-14 20:05 ` [PATCH v2 5/5] coccicheck: refer to coccicheck bottest wiki for documentation Luis R. Rodriguez
2016-06-14 20:19 ` [PATCH v2 0/5] coccicheck: extend with parmap and indexing heuristics Luis R. Rodriguez
2016-06-14 20:23 ` [PATCH v3 0/6] " Luis R. Rodriguez
2016-06-14 20:23 ` [PATCH v3 1/6] coccicheck: move spatch binary check up Luis R. Rodriguez
2016-06-14 20:23 ` [PATCH v3 2/6] coccicheck: enable parmap support Luis R. Rodriguez
2016-06-14 20:23 ` [PATCH v3 3/6] scripts: add glimpse.sh for indexing the kernel Luis R. Rodriguez
2016-06-15 10:26 ` Aw: [Cocci] " SF Markus Elfring
2016-06-15 18:00 ` Luis R. Rodriguez [this message]
2016-06-15 18:24 ` SF Markus Elfring
2016-06-15 18:43 ` Luis R. Rodriguez
2016-06-17 16:05 ` SF Markus Elfring
2016-06-17 17:23 ` Luis R. Rodriguez
2016-06-14 20:23 ` [PATCH v3 4/6] coccicheck: add indexing enhancement options Luis R. Rodriguez
2016-06-15 11:20 ` Aw: [Cocci] " SF Markus Elfring
2016-06-15 20:00 ` Luis R. Rodriguez
2016-06-14 20:23 ` [PATCH v3 5/6] coccicheck: document how to pass extra options to coccinelle Luis R. Rodriguez
2016-06-14 20:23 ` [PATCH v3 6/6] coccicheck: refer to coccicheck bottest wiki for documentation Luis R. Rodriguez
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=20160615180000.GW11948@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=Gilles.Muller@lip6.fr \
--cc=cocci@systeme.lip6.fr \
--cc=elfring@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--cc=nicolas.palix@imag.fr \
/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®