From: Andrew Warfield <andrew.warfield@gmail.com>
To: aq <aquynh@gmail.com>
Cc: Kip Macy <kip.macy@gmail.com>, xen-devel <xen-devel@lists.xensource.com>
Subject: Re: lxr.xensource.com ?
Date: Wed, 18 May 2005 07:58:58 +0100 [thread overview]
Message-ID: <eacc82a405051723584492bfa3@mail.gmail.com> (raw)
In-Reply-To: <9cde8bff05051723371839352@mail.gmail.com>
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
>
next prev parent reply other threads:[~2005-05-18 6:58 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 [this message]
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
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=eacc82a405051723584492bfa3@mail.gmail.com \
--to=andrew.warfield@gmail.com \
--cc=andrew.warfield@cl.cam.ac.uk \
--cc=aquynh@gmail.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.