From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] interprocess shared files
Date: Thu, 14 May 2015 18:32:52 -0400 [thread overview]
Message-ID: <20150414183252.eklhad@comcast.net> (raw)
In-Reply-To: <20150514220013.GI2917@toaster.adamthompson.me.uk>
> I've slightly altered this such that we now don't need ++.o versions.
Excellent! I thought about that but didn't realize it would work so cleanly.
Will that sort of interoperability hold for other compilers?
Anyways I applied the same change to makefile.bsd,
which I try to keep up to date even though I don't really have a good way
to test it.
Karl Dahlke
next prev parent reply other threads:[~2015-05-14 22:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 19:55 Karl Dahlke
2015-05-14 22:00 ` Adam Thompson
2015-05-14 22:32 ` Karl Dahlke [this message]
2015-05-14 22:39 ` Adam Thompson
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=20150414183252.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).