From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] windows port
Date: Fri, 25 Sep 2015 16:24:15 -0400 [thread overview]
Message-ID: <20150825162415.eklhad@comcast.net> (raw)
Geoff is working on the windows port and making good progress.
I have suspended other work,
so I can fold some of his C changes into our master branch,
so he can follow our branch as it evolves without having to refix
things he has fixed before.
My next few pushes will probably be small C changes
so that gcc and windows visual c are both happy.
If you all could refrain from pushing changes until this is done that would be great,
unless of course the push fixes a seg fault or something vital.
So many good things are happening now -
I wonder if we have finally reached critical mass.
Karl Dahlke
next reply other threads:[~2015-09-25 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 20:24 Karl Dahlke [this message]
2015-09-25 21:00 ` Chris Brannon
2015-09-25 21:54 ` Adam Thompson
2015-09-26 3:28 ` [Edbrowse-dev] html.c:757 Kevin Carhart
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=20150825162415.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/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 NNTP newsgroup(s).