All of lore.kernel.org
 help / color / mirror / Atom feed
From: aq <aquynh@gmail.com>
To: James Bulpin <james@xensource.com>
Cc: Andrew Warfield <Andrew.Warfield@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.xensource.com>,
	Kip Macy <kip.macy@gmail.com>
Subject: Re: lxr.xensource.com ?
Date: Thu, 19 May 2005 00:36:08 +0900	[thread overview]
Message-ID: <9cde8bff05051808366ddb53e6@mail.gmail.com> (raw)
In-Reply-To: <1116411741.19604.370.camel@plym.cl.cam.ac.uk>

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

  reply	other threads:[~2005-05-18 15:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18  6:27 lxr.xensource.com ? aq
2005-05-18  6:30 ` Kip Macy
2005-05-18  6:37   ` aq
2005-05-18  6:58     ` Andrew Warfield
2005-05-18  7:20       ` aq
2005-05-18  9:43         ` James Bulpin
2005-05-18 10:22           ` James Bulpin
2005-05-18 15:36             ` aq [this message]
2005-05-18 15:50               ` James Bulpin

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=9cde8bff05051808366ddb53e6@mail.gmail.com \
    --to=aquynh@gmail.com \
    --cc=Andrew.Warfield@cl.cam.ac.uk \
    --cc=james@xensource.com \
    --cc=kip.macy@gmail.com \
    --cc=xen-devel@lists.xensource.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 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.