From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] shared libraries
Date: Tue, 18 Apr 2006 19:57:18 +0100 [thread overview]
Message-ID: <4edf670da613d13c2ae28a0addad357f@terzarima.net> (raw)
In-Reply-To: <2b92b534191b5621c87d58c5f10b56eb@cat-v.org>
> Sorry for deciding that maybe it was better idea to try to work with
> Charles rather than duplicating even more work.
the thing you keep forgetting is that this sort of thing takes my
spare time, and that's been limited for a time, even the time to wade
through sourceforge conventions.
next prev parent reply other threads:[~2006-04-18 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-18 17:54 Russ Cox
2006-04-18 17:03 ` Charles Forsyth
2006-04-18 18:14 ` Russ Cox
2006-04-18 17:17 ` Charles Forsyth
2006-04-18 17:25 ` Bruce Ellis
2006-04-18 17:39 ` uriel
2006-04-18 18:03 ` uriel
2006-04-18 18:57 ` Charles Forsyth [this message]
2006-04-18 19:20 ` Russ Cox
2006-04-18 20:46 ` Ronald G Minnich
2006-04-18 21:21 ` Rob Pike
2006-04-18 21:26 ` Brantley Coile
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=4edf670da613d13c2ae28a0addad357f@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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).