From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] FreeBSD port
Date: Sat, 18 Jan 2014 20:00:31 -0500 [thread overview]
Message-ID: <20140018200031.eklhad@comcast.net> (raw)
In-Reply-To: <20140118070132.GA6130@vmailbox.org>
> There were only minimal changes required to install it
Would it make sense to push some of these changes into the main branch,
or are they very bsd specific?
Maybe conditional compilation #ifdef FREEBSD
Is there a way I might look at those changes and evaluate?
I just want to make future ports easier.
Karl Dahlke
next prev parent reply other threads:[~2014-01-19 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-18 7:01 David Vionnet
2014-01-18 17:15 ` Cleverson Casarin Uliana
2014-01-18 17:46 ` Chris Brannon
2014-01-18 18:09 ` Cleverson Casarin Uliana
2014-01-19 1:00 ` Karl Dahlke [this message]
2014-01-19 1:53 ` Chris Brannon
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=20140018200031.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).