From: Jon Masters <jcm@redhat.com>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: devzero@web.de, linux-kernel@vger.kernel.org
Subject: Re: [RFC] - LXR on kernel.org ? was: Re: What tools to use?
Date: Mon, 14 May 2007 18:40:49 -0400 [thread overview]
Message-ID: <1179182449.32158.32.camel@jcmlaptop> (raw)
In-Reply-To: <20070514194451.GN27871@lug-owl.de>
On Mon, 2007-05-14 at 21:44 +0200, Jan-Benedict Glaw wrote:
> 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:
> > 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.)
This is what I was interested in getting setup. I'm away on vacation
this week (I'm currently out on the road to Yosemite and about to have
no email whatsoever), but I just asked an intern of mine to start
looking into it and will followup when I get back next week.
Please keep me copied on any mail.
Jon.
prev parent reply other threads:[~2007-05-14 22:41 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
2007-05-14 22:40 ` Jon Masters [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=1179182449.32158.32.camel@jcmlaptop \
--to=jcm@redhat.com \
--cc=devzero@web.de \
--cc=jbglaw@lug-owl.de \
--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.