From: forsyth@vitanuova.com forsyth@vitanuova.com
Subject: [9fans] 3rd edition documentation
Date: Thu, 8 Jun 2000 20:35:12 +0100 [thread overview]
Message-ID: <20000608193512.WC9U5q6Bt40ARImaPACtqXzEr-joKNNP_HpyFRdm7Is@z> (raw)
>>Don't know - I was just going by the fact that the 2nd release
>>manuals have the AT&T logo on the spine, and were Copyright AT&T.
AT&T split itself into independent bits later, Lucent being one.
>>I am not sure how ownership/responsibility is divided amoungst
>>AT&T, Lucent, Bell Labs, Harcourt Brace, Vita Nuova etc.
Lucent owns Plan 9 and licences it (using the licence you will have
seen on the Bell Labs distribution site).
>>Is it perhaps the case the Harcourt Brace was engaged by AT&T
>>as exclusive packager/distributor for the second release, and
>>Vita Nuova is the first of possibly many non-exclusive
>>packer/distributors of Lucent's release.?
I don't know what the HB arrangement was, but I can say definitively
that we are not `engaged' to do this by Lucent.
>>It isn't obvious to me if Lucent will be printing and selling
>>documentation to resellers and end-users, or if the resellers
>>will be responsible for arranging their own printing.
Vita does its own publishing (we pay someone to do the actual printing
but we prepare the printer-ready files, organise art work, CDs).
next reply other threads:[~2000-06-08 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-08 19:35 forsyth [this message]
[not found] <003401bfd182$3a5a18c0$5d0101c8@hcinet>
2000-06-08 22:33 ` Jim Choate
-- strict thread matches above, loose matches on Subject: below --
2000-06-08 19:46 Michael
2000-06-08 19:25 rob
2000-06-08 19:18 Digby
2000-06-08 18:50 Digby
2000-06-08 18:07 forsyth
2000-06-08 17:43 mike
2000-06-08 17:28 Digby
2000-06-08 17:15 Digby
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=20000608193512.WC9U5q6Bt40ARImaPACtqXzEr-joKNNP_HpyFRdm7Is@z \
--to=forsyth@vitanuova.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).