From: Sam Vilain <sam@vilain.net>
To: "Guillermo López Alejos" <glalejos@gmail.com>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Introducting LXD
Date: Wed, 22 Mar 2006 11:15:32 +1200 [thread overview]
Message-ID: <44208914.9020604@vilain.net> (raw)
In-Reply-To: <4fec73ca0603210212m5b351a14t678ee6dc918a5eb2@mail.gmail.com>
Guillermo López Alejos wrote:
>Dear Linux developers,
>
>I am student of Computer Sciences at University Carlos III of Madrid
>(Spain). I worked before in a project related with the Linux kernel,
>analyzing the integration of the parallel file system expand into the
>Linux kernel.
>
>Actually, I am developing LXD as my final year project. LXD, based on
>the LXR project, intends to be a documentation system for large source
>projects. Its main objective is to gather high level information that
>cannot be extracted from the source files. LXD is registered at
>SourceForge.net (http://sourceforge.net/projects/lxd/). A detailed
>presentation for the LXD project can be found at
>http://lxd.sourceforge.net/.
>
>It is of my interest to analyze the user requirements for LXD. I will
>appreciate very much any comment about LXD, especially those regarding
>the expected system usage. There is a mailing list available at
>http://lists.sourceforge.net/lists/listinfo/lxd-devel for those
>interested in discussing LXD capabilities.
>
>
Sounds very generic, I'd say a lot of software fits into this category.
Perhaps you'd like to list a few of the novel things that you attempt to
achieve, and the scope of your problem set. Is this just C code?
Yes, I could follow the link, but there was nothing really there in your
post to make me want to bite.
Sam.
next prev parent reply other threads:[~2006-03-21 23:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 10:12 Introducting LXD Guillermo López Alejos
2006-03-21 23:15 ` Sam Vilain [this message]
2006-03-22 10:45 ` Guillermo López Alejos
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=44208914.9020604@vilain.net \
--to=sam@vilain.net \
--cc=glalejos@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox