From: Jody Lee Bruchon <jody@jodybruchon.com>
To: Royce Williams <royce@tycho.org>, ELKS <linux-8086@vger.kernel.org>
Subject: Re: Where does ELKS need to go?
Date: Sat, 19 Apr 2014 14:33:07 -0400 [thread overview]
Message-ID: <14864cbe-c6e2-4c36-9c19-ec5dc3fe24bc@email.android.com> (raw)
In-Reply-To: <CA+E3k906ExjzWH=6WdY-KaFWDQHbupkX4q=dK_PQw8NAxCDYkQ@mail.gmail.com>
On April 19, 2014 2:28:44 PM EDT, Royce Williams <royce@tycho.org> wrote:
>Generally speaking, prioritizing a
>minimum baseline of "installability" would really help more people be
>able to test -- by reducing the friction and startup cost of testing.
You are right, and I think I can make that happen. Let me put my nose to the grindstone for a while and see if I can get together something that will make ELKS installable and bootable from a hard drive with less difficulty. That won't be a huge amount of work and will definitely close a big gap that has plagued ELKS from the start.
-Jody
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2014-04-19 18:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-05 1:12 ELKS links broken Michael Sklaroff
2014-04-18 19:26 ` Edoardo Liverani
2014-04-18 20:03 ` Where does ELKS need to go? (was: ELKS links broken) Jody Bruchon
2014-04-18 21:44 ` Edoardo Liverani
2014-04-19 16:45 ` Where does ELKS need to go? Harley Laue
2014-04-19 18:28 ` Royce Williams
2014-04-19 18:33 ` Jody Lee Bruchon [this message]
2014-04-19 20:38 ` Royce Williams
2014-04-19 22:29 ` Edoardo Liverani
2014-04-21 22:05 ` David Given
2014-04-19 18:07 ` Where does ELKS need to go? (was: ELKS links broken) Chad
2014-04-19 20:43 ` Royce Williams
2014-04-19 21:14 ` Jody Bruchon
-- strict thread matches above, loose matches on Subject: below --
2014-04-21 12:04 Where does ELKS need to go? LM
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=14864cbe-c6e2-4c36-9c19-ec5dc3fe24bc@email.android.com \
--to=jody@jodybruchon.com \
--cc=linux-8086@vger.kernel.org \
--cc=royce@tycho.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