From: Michael Taylor <michael.taylor@ec.gc.ca>
To: Paul Gimpelj <pgimpelj@sympatico.ca>
Cc: linux-c-programming <linux-c-programming@vger.kernel.org>
Subject: Re: LILO repository cvs head where is?
Date: Thu, 03 Jun 2004 10:24:21 -0400 [thread overview]
Message-ID: <40BF3495.3030804@ec.gc.ca> (raw)
In-Reply-To: <003201c44848$dfd8f780$3410fea9@zoom>
Paul Gimpelj wrote:
> Hi,
>
> can anyone tell me where root cvs is located for lilo?
>
> and its developer mailing list?
I don't think there is a public CVS repository for LILO, and I don't know if
there is a mailing list.
The current home for LILO appears to be
<http://lilo.go.dyndns.org/>
and the source files are at
<http://home.san.rr.com/johninsd/pub/linux/lilo/>
An Q&A forum where the main developer, John Coffman is active, is at
<http://freshmeat.net/projects/lilo/>
prev parent reply other threads:[~2004-06-03 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 2:25 LILO repository cvs head where is? Paul Gimpelj
2004-06-03 14:24 ` Michael Taylor [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=40BF3495.3030804@ec.gc.ca \
--to=michael.taylor@ec.gc.ca \
--cc=linux-c-programming@vger.kernel.org \
--cc=pgimpelj@sympatico.ca \
/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;
as well as URLs for NNTP newsgroup(s).