From: Jody <jbruchon@nc.rr.com>
To: Linux-8086 <linux-8086@vger.kernel.org>
Subject: ELKS-CVS dump
Date: Fri, 05 May 2006 01:02:18 -0400 [thread overview]
Message-ID: <445ADC5A.4050406@nc.rr.com> (raw)
Regarding ELKS-0.1.3:
First of all, that was a CVS dump I grabbed when I noticed that the
0.1.3 notice had appeared somewhere but never got released on SF. It
may not actually be 0.1.3 in truth, but it is as close as I could get at
the time, and I wanted all of you to have something to hack at. That
being said, I'm about to help all of you work around the CVS problem
we've got right now.
This is especially addressed to Tom McCabe: thank you so much for your
bug reports from the 0.1.3 tarball I released. I am now providing the
ELKS files from CVS that I recently grabbed and somehow managed to get
to my machine, and it has basically ALL of the patches you brought up
already in place. I'm hosting it personally on my home net, so here's
where all of you can get the ELKS CVS tarball as of 2006-05-03:
http://compsolutions.ath.cx:88/elks/
I will add archives here as patches are submitted to make sure we're all
up to date. I may self-host some of the tools such as Dev86 for
completeness, also, just so we have a backup plan.
Please mail or CC all patches to elks@jodybruchon.com for testing,
inclusion, and release.
Thank you all!
Jody Bruchon
reply other threads:[~2006-05-05 5:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=445ADC5A.4050406@nc.rr.com \
--to=jbruchon@nc.rr.com \
--cc=linux-8086@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 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.