From: Jim Choate <ravage@einstein.ssz.com>
To: <9fans@cse.psu.edu>
Cc: <hangar18-general@open-forge.org>
Subject: Re: [9fans] Q: Using Plan 9 documentation in talks?
Date: Sat, 14 Dec 2002 07:06:30 -0600 [thread overview]
Message-ID: <Pine.LNX.4.33.0212140704270.10976-100000@einstein.ssz.com> (raw)
In-Reply-To: <119346380.1039764142@[192.168.0.2]>
Thanks to all those who provided feedback. I'llt take it in the proper
consideration.
Since I never got an answer regarding correct citation in regards
copyright (ie single or multiple) I've decided to use none of the
Lucent/Bell Labs material directly.
--
____________________________________________________________________
We don't see things as they are, ravage@ssz.com
we see them as we are. www.ssz.com
jchoate@open-forge.org
Anais Nin www.open-forge.org
--------------------------------------------------------------------
next prev parent reply other threads:[~2002-12-14 13:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 8:30 [9fans] updates on sources Russ Cox
2002-12-13 13:40 ` [9fans] Q: Using Plan 9 documentation in talks? Jim Choate
2002-12-13 15:22 ` matt
2002-12-13 15:22 ` rob pike
2002-12-14 13:06 ` Jim Choate [this message]
2002-12-13 15:11 Fco.J.Ballesteros
2002-12-13 15:18 ` andrey mirtchovski
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=Pine.LNX.4.33.0212140704270.10976-100000@einstein.ssz.com \
--to=ravage@einstein.ssz.com \
--cc=9fans@cse.psu.edu \
--cc=hangar18-general@open-forge.org \
/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).