From: David Given <dg@cowlark.com>
To: linux-8086 <linux-8086@vger.kernel.org>
Subject: Current project repo?
Date: Thu, 15 Nov 2012 12:04:40 +0000 [thread overview]
Message-ID: <50A4DA58.9080107@cowlark.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
What with the recent changes, I've just tried to rebuild ELKS to see how
it runs on a nasty 486 palmtop I have. My understanding is that the CVS
repository is now dead, and development has moved to the Sourceforge git
repo at git://elks.git.sourceforge.net/gitroot/elks/elks.
However, I've just tried building it and have run into some simple but
showstopping issues; am I looking in this the right place? If so I'll
clean up my fixes and send them to the mailing list. If not, well, I'll
start again with the right source tree...
--
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│ "There does not now, nor will there ever, exist a programming
│ language in which it is the least bit hard to write bad programs." ---
│ Flon's Axiom
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
reply other threads:[~2012-11-15 12:04 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=50A4DA58.9080107@cowlark.com \
--to=dg@cowlark.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).