From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Michael Opdenacker <michael-lists@free-electrons.com>
Cc: Jan Kiszka <jan.kiszka@googlemail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: New Linux Cross Reference (LXR) site
Date: Mon, 29 May 2006 10:59:02 +0200 [thread overview]
Message-ID: <20060529085901.GV13513@lug-owl.de> (raw)
In-Reply-To: <447AB5C9.4060901@free-electrons.com>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
On Mon, 2006-05-29 10:50:17 +0200, Michael Opdenacker <michael-lists@free-electrons.com> wrote:
> >Recently I started to experiment with OpenGrok
> >(http://www.opensolaris.org/os/project/opengrok), also for kernel
> >trees. Quite easy to handle, and I was enthusiastic about it first.
> >But it is not yet as robust as the lxr behind your site (reference
> >links are occasionally missing in the code), it's history mechanism is
> >not comparable to lxr's versioning, and arch-switching is lacking.
>
> Thanks for the tip! I will keep an eye on this new tool too...
Seems to be highly interwoven mit the used SCM system and thus does
also do some tasks like searching in the commit messages etc., so its
scope is a bit different than that of LXR. Also, it's not GPLed.
MfG, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de . +49-172-7608481 _ O _
"Eine Freie Meinung in einem Freien Kopf | Gegen Zensur | Gegen Krieg _ _ O
für einen Freien Staat voll Freier Bürger" | im Internet! | im Irak! O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-05-29 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-24 9:03 Michael Opdenacker
2006-05-27 17:25 ` Jan Kiszka
2006-05-29 8:50 ` Michael Opdenacker
2006-05-29 8:59 ` Jan-Benedict Glaw [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=20060529085901.GV13513@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=jan.kiszka@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael-lists@free-electrons.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
Powered by JetHome