From: Steve Kotsopoulos steve@border.com
Subject: duplication of the anti-effort-duplication effort
Date: Mon, 18 Nov 1996 20:17:18 -0500 [thread overview]
Message-ID: <19961119011718.JSSmnAOSuXTin5H_h1dKpquuu6H5Tm0IBGkX8Lp49Fo@z> (raw)
Russ Cox <rsc@research.att.com> wrote:
> Project list web page at
> http://cm.bell-labs.com/who/rsc/plan9/index.html
> Comments, suggestions welcome.
There is already a projects area in the Plan 9 faq.
It is under Subject: How can I get involved?
It also says:
:> If anyone would like their projects listed here, let me know. This should
:> help prevent duplication of effort, and increase involvment from the 'net
:> community. If you are looking for a list of suggested project topics, see
:> http://www.ecf.toronto.edu/plan9/info/projects
--
Steve Kotsopoulos Research and Development, BorderWare Firewall Server
steve@border.com Secure Computing Canada Ltd. http://www.border.com
next reply other threads:[~1996-11-19 1:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-11-19 1:17 Steve [this message]
1996-11-19 1:51 Russ
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=19961119011718.JSSmnAOSuXTin5H_h1dKpquuu6H5Tm0IBGkX8Lp49Fo@z \
--to=9fans@9fans.net \
/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).