lxr.xensource.com ?

lxr.xensource.com ?

[aq]

hello,

looks like lxr.xensource.com is not completed? nobody here takes care this site?

regards,
aq

Re: lxr.xensource.com ?

[Kip Macy]

What is missing?
       -Kip

On 5/17/05, aq <aquynh@gmail.com> wrote:
> hello,
> 
> looks like lxr.xensource.com is not completed? nobody here takes care this site?
> 
> regards,
> aq
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

Re: lxr.xensource.com ?

[aq]

On 5/18/05, Kip Macy <kip.macy@gmail.com> wrote:
> What is missing?
>       -Kip
> 

for example, this dir is empty/non-existent:
http://lxr.xensource.com/lxr-unstable/source/tools/?v=tools-xen-unstable

or we should assume that unstable's lxr will not be updated ?

regards,
aq

> On 5/17/05, aq <aquynh@gmail.com> wrote:
> > hello,
> >
> > looks like lxr.xensource.com is not completed? nobody here takes care this site?
> >
> > regards,
> > aq
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xensource.com
> > http://lists.xensource.com/xen-devel
> >
>

Re: lxr.xensource.com ?

[Andrew Warfield]

Tools are there, the paths in lxr are just a little strange.  The olls
is at the root of the top-level tools tree, rather than being under
unstable as it is in the real repository.  If you look here:

   http://lxr.xensource.com/lxr-unstable/source/?v=tools-xen-unstable

you should find them.

a.

On 5/18/05, aq <aquynh@gmail.com> wrote:
> On 5/18/05, Kip Macy <kip.macy@gmail.com> wrote:
> > What is missing?
> >       -Kip
> >
> 
> for example, this dir is empty/non-existent:
> http://lxr.xensource.com/lxr-unstable/source/tools/?v=tools-xen-unstable
> 
> or we should assume that unstable's lxr will not be updated ?
> 
> regards,
> aq
> 
> > On 5/17/05, aq <aquynh@gmail.com> wrote:
> > > hello,
> > >
> > > looks like lxr.xensource.com is not completed? nobody here takes care this site?
> > >
> > > regards,
> > > aq
> > >
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@lists.xensource.com
> > > http://lists.xensource.com/xen-devel
> > >
> >
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

Re: lxr.xensource.com ?

[aq]

On 5/18/05, Andrew Warfield <andrew.warfield@gmail.com> wrote:
> Tools are there, the paths in lxr are just a little strange.  The olls
> is at the root of the top-level tools tree, rather than being under
> unstable as it is in the real repository.  If you look here:
> 
>   http://lxr.xensource.com/lxr-unstable/source/?v=tools-xen-unstable
> 
> you should find them.
> 

i checked again, looks like you have just fixed all the links. it is
allright now.

the only problem is the -unstable is not updated very often.
-- 
regards,
aq

Re: lxr.xensource.com ?

[James Bulpin]

On Wed, 2005-05-18 at 07:27, aq wrote: 
> looks like lxr.xensource.com is not completed? nobody here takes care this site?

We do monitor the top level and a selection of key pages, just not every
single page.

>http://lxr.xensource.com/lxr-unstable/source/tools/?v=tools-xen-unstable

How did you come by this URL - was it a link from another LXR page (in
which case we need to fix it) or way it manually crafted?

On Wed, 2005-05-18 at 08:20, aq wrote:
> On 5/18/05, Andrew Warfield <andrew.warfield@gmail.com> wrote:
> > Tools are there, the paths in lxr are just a little strange.  The olls
> > is at the root of the top-level tools tree, rather than being under
> > unstable as it is in the real repository.  If you look here:
> > 
> >   http://lxr.xensource.com/lxr-unstable/source/?v=tools-xen-unstable
> > 
> > you should find them.

This came from a desire from some developers to not have crosslinking
between e.g. Xen and tools and Xen and Linux where similar symbols may
used but aren't related.

> i checked again, looks like you have just fixed all the links. it is
> allright now.

Strange, no changes have been made during the course of this
conversation.

> the only problem is the -unstable is not updated very often.

We run the updates weekly. I'm happy to increase the frequency of this
if there is the demand.

As ever, suggestions, fault reports, etc. are welcome.

Regards,

James

Re: lxr.xensource.com ?

[James Bulpin]

On Wed, 2005-05-18 at 10:43, James Bulpin wrote:
> On Wed, 2005-05-18 at 07:27, aq wrote: 
> > looks like lxr.xensource.com is not completed? nobody here takes care this site?
> 
> We do monitor the top level and a selection of key pages, just not every
> single page.
> 
> >http://lxr.xensource.com/lxr-unstable/source/tools/?v=tools-xen-unstable
> 
> How did you come by this URL - was it a link from another LXR page (in
> which case we need to fix it) or way it manually crafted?

After chatting with Andy just now I'll answer my own question. This link
was probably a result of navigating to the tools directory of the xen
(hypervisor only) tree (contains figlet) then clicking the
"tools-xen-unstable" link. LXR always moves to the same path in the new
tree (useful when comparing e.g. two versions of linux). As we are
(ab)using LXR for various trees, a file or directory in one will not
necessarily appear in the other, hence the error. Short of hacking the
LXR code there isn't much we can do about this. Anyone know of a more
flexible web-based source code browser?

Cheers,

James

Re: lxr.xensource.com ?

[aq]

On 18 May 2005 11:22:21 +0100, James Bulpin <james@xensource.com> wrote:
> On Wed, 2005-05-18 at 10:43, James Bulpin wrote:
> > On Wed, 2005-05-18 at 07:27, aq wrote:
> > > looks like lxr.xensource.com is not completed? nobody here takes care this site?
> >
> > We do monitor the top level and a selection of key pages, just not every
> > single page.
> >
> > >http://lxr.xensource.com/lxr-unstable/source/tools/?v=tools-xen-unstable
> >
> > How did you come by this URL - was it a link from another LXR page (in
> > which case we need to fix it) or way it manually crafted?
> 
> After chatting with Andy just now I'll answer my own question. This link
> was probably a result of navigating to the tools directory of the xen
> (hypervisor only) tree (contains figlet) then clicking the
> "tools-xen-unstable" link.

yes, that is exactly how i got the broken links.

but why you layout the code differently from the way it layouts when
untar? i am used to lxr.linux.no, so i got confused when first seen
lxr.xensource.com. perhaps layout it in normal way will solve this
problem?

about updating the site, i guess only -unstable needs to be updated
often. -testing is more stable and needs to care less.
-- 
regards,
aq

Re: lxr.xensource.com ?

[James Bulpin]

On Wed, 2005-05-18 at 16:36, aq wrote:
> but why you layout the code differently from the way it layouts when
> untar? i am used to lxr.linux.no, so i got confused when first seen
> lxr.xensource.com. perhaps layout it in normal way will solve this
> problem?

The layout isn't really different, we just index different parts of the
tree separately. LXR can only handle separate index domains as separate
trees hence the view we get.

The "normal way" at lxr.linux.no is fine if you just have linux trees.
We *could* just index the whole of the -unstable or -testing release as
a single large tree, including Xen, the tools, both linux versions, both
BSD versions, but, as mentioned before, that crossreferences stuff that
really doesn't relate at the C symbol level.

> about updating the site, i guess only -unstable needs to be updated
> often. -testing is more stable and needs to care less.

Good point. Let's go with daily for -unstable and weekly for -testing.
I'll make the changes tomorrow.

Cheers,

James