From: Jody Bruchon <jody@jodybruchon.com>
To: ELKS <linux-8086@vger.kernel.org>
Subject: Help test recent Dev86 changes against ELKS
Date: Tue, 1 Dec 2015 06:52:48 -0500 [thread overview]
Message-ID: <565D8A10.3060707@jodybruchon.com> (raw)
There have been some changes to Dev86 over the past week or so. I don't
want to pull those changes into my fork of the code unless they compile
a working ELKS environment. Unfortunately, I don't have time to test
these changes right now, so I'd like to see if anyone here would help
out. The current Dev86 tree is here:
https://github.com/lkundrak/dev86
My Dev86 tree is here:
https://github.com/jbruchon/dev86
If someone is able to compile a booting and working ELKS with the recent
changes, let me know and I'll pull them into my tree ASAP.
-Jody
next reply other threads:[~2015-12-01 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-01 11:52 Jody Bruchon [this message]
[not found] ` <565DF1C6.3000105@gmx.net>
2015-12-01 19:37 ` Help test recent Dev86 changes against ELKS 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=565D8A10.3060707@jodybruchon.com \
--to=jody@jodybruchon.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).