From: Gregg Levine <gregg.drwho8@gmail.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Retrieving ELKS source code and building it
Date: Sat, 13 Jun 2015 11:26:58 -0400 [thread overview]
Message-ID: <CAC5iaNGyKQweiDQp=hojcrZv5Nq_L-B1DTPVge_JfoEuSmgTrg@mail.gmail.com> (raw)
Hello!
Usual middle of the year projects surfacing here.
What is the approved method of retrieving the source code and source
for tools, to build and eventually make use of ELKS?
I confess I have not been keeping up with the resurgence in activity
on the entire list.
-----
Gregg C Levine gregg.drwho8@gmail.com
"This signature fought the Time Wars, time and again."
next reply other threads:[~2015-06-13 15:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-13 15:26 Gregg Levine [this message]
2015-06-13 15:28 ` Retrieving ELKS source code and building it Jody Bruchon
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='CAC5iaNGyKQweiDQp=hojcrZv5Nq_L-B1DTPVge_JfoEuSmgTrg@mail.gmail.com' \
--to=gregg.drwho8@gmail.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).