All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arne Georg Gleditsch <argggh@dolphinics.no>
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: 11 May 2007 10:56:33 +0200	[thread overview]
Message-ID: <873b23ivr2.fsf@pelargir.dolphinics.no> (raw)
In-Reply-To: <1783741195@web.de>

devzero@web.de writes:
> 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 " ?
> 
> over the years, i have downloaded tons of kernels for this, very much
> waste of bandwidth and time - because whenever i need to take a look,
> i have no recent kernel source around - so i need to download that big
> thing and go trough that untar orgy. having recent
> browsable/searchable and easy to find lxr`ed kernel-source online
> would be really great
> 
> i seldom find lxr for current kernels on the net, so i just wonder:
> [..]

I maintain the original LXR site at lxr.linux.no, which unfortunately
tends to lag behind quite a bit.  This is partly due to lack of time
to keep it current on my part, but also due to the fact that adding
new kernels to the version running on lxr.linux.no is a bit more time
and resource-consuming than it ought to be.  Better support for both
incremental indexing and git-based repos is forthcoming, and I hope
the situation will improve a bit with that.  I'll keep you posted.

-- 
								Arne.


  parent reply	other threads:[~2007-05-11  8:56 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 [this message]
2007-05-11 12:25   ` Chris Smith
2007-05-11 13:44     ` Robin Getz
2007-05-14 19:44 ` Jan-Benedict Glaw
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=873b23ivr2.fsf@pelargir.dolphinics.no \
    --to=argggh@dolphinics.no \
    --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.