From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] shared libraries
Date: Tue, 18 Apr 2006 14:20:37 -0500 [thread overview]
Message-ID: <52002995dcc16a465082e363549d4d66@swtch.com> (raw)
In-Reply-To: <e24e95b9e6d5155e3c96974165150575@cat-v.org>
> That is exactly what I proposed to Charles over a year ago, I'm still
> waiting for access, I calculate it should take 5 min max to fix it.
no. what i said was that nothing is stopping you from
making a new project (called, say kcc) and populating
its pages as you see fit. nothing, that is, except that then
you'd have one less thing to complain about.
russ
next prev parent reply other threads:[~2006-04-18 19:20 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
2006-04-18 19:20 ` Russ Cox [this message]
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=52002995dcc16a465082e363549d4d66@swtch.com \
--to=rsc@swtch.com \
--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).