All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org, jcm@redhat.com
Subject: Re: [RFC] - LXR on kernel.org ? was: Re: What tools to use?
Date: Mon, 14 May 2007 21:44:51 +0200	[thread overview]
Message-ID: <20070514194451.GN27871@lug-owl.de> (raw)
In-Reply-To: <1783741195@web.de>

[-- Attachment #1: Type: text/plain, Size: 3140 bytes --]

On Fri, 2007-05-11 10:06:17 +0200, devzero@web.de <devzero@web.de> wrote:
> Jesper Juhl <jesper.juhl () gmail ! com> wrote:
> > On 10/05/07, Shahbaz Khan <shaz.linux@gmail.com> wrote:
> > > All the experts on this list plz let me know of any good cross
> > > referencing tool for source code navigation. I have tried LXR but its
> > > not easy to configure for a rookie like me. Anyother as good as LXR?
> > >
> > lxr is pretty good (glimpse on its own as well can be useful). If you
> > don't want to set it up yourself, then you could consider to use the
> > online version at http://lxr.linux.no/

One "problem" with lxr.linux.no is that it's only updated from time to
time.  Maximilian Wilhelm and I added some preliminary GIT support to
LXR, and we're working on a patch to present the list of versions as
drop-down boxes (instead of a long link list.)

This should allow to index all and any tagged versions of the Linux
kernel and present them.  However, I don't have a box that's equipped
properly (HDD, CPU as well as network connectivity) to offer such a
setup, but I'd help in setting it up if somebody provides the machine!

> > Another good thing is "make ctags" in the kernel source dir - this
> > will  let you quickly jump to declarations etc and back with a few
> > simple keystrokes in editors like vim.
> > http://www.faqs.org/docs/ldev/0130091154_64.htm
> > http://applications.linux.com/article.pl?sid=07/01/22/167212&tid=13&tid=47
> > http://cscope.sourceforge.net/cscope_vim_tutorial.html
> > 
> > "make cscope" is another good option. It'll generate an index usable
> > by the cscope tool (http://cscope.sourceforge.net/).
> 
> I like lxr pretty much.
> i`m not a programmer, but i often need some information on "what`s
> the driver version of xyz in latest kernel" or "was this or that
> feature/patch already being merged" or "i have this line of code
> in kernel - how does it look in recent kernel , did it change " ?

You can easily get this information from http://git.kernel.org/git .

> why not adding a link to every kernel an kernel.org kernel,
> pointing to recent lxr`ed kernel source - or - even better -
> make lxr`ed kernel source part of kernel.org (so we
> have "B V VI 	C Changelog LXR" ) ? 

I'd support the idea, but somebody needs to offer a machine or two and
enough bandwidth. (Though I hope that it's used rarely enough so that
only one machine is needed.)

> sure, i know kernel.org itself is very busy, but maybe this can
> be done via dedicated lxr machine/webserver someone is willing
> to donate !?

There's *no* way to add this to the current kernel.org machines.
There's quite some DB access during indexing, and making up the
sources on request takes some CPU cycles, too.

> for myself, i would happily donate some bucks for this.

As I said: If you manage to prepare the box, I'll offer to do the LXR
setup and automate the indexing.

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
 Signature of:                      http://perl.plover.com/Questions.html
 the second  :

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-05-14 19:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-11  8:06 [RFC] - LXR on kernel.org ? was: Re: What tools to use? devzero
2007-05-11  8:35 ` Jesper Juhl
2007-05-11  8:56 ` Arne Georg Gleditsch
2007-05-11 12:25   ` Chris Smith
2007-05-11 13:44     ` Robin Getz
2007-05-14 19:44 ` Jan-Benedict Glaw [this message]
2007-05-14 22:40   ` Jon Masters

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=20070514194451.GN27871@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=devzero@web.de \
    --cc=jcm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.