9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Laura Creighton <lac@strakt.com>
To: 9fans@cse.psu.edu
Subject: [9fans] licensing agreement preventing disclosure of hardware manuals.
Date: Sat, 29 Nov 2003 18:13:36 +0100	[thread overview]
Message-ID: <200311291713.hATHDaQg029076@ratthing-b246.strakt.com> (raw)

Could any of you who have asked for hardware manuals and been turned
down either a) because they say it will invalidate their patents or
b) because they say it will invalidate tehir licensing agreement
with somebody -- say Microsoft -- to release such details please
mail me the names of 'what hardware you wanted specs for' and
'why you didn't get it'.  I'm looking for evidence of abuse of
monopoly position or improper secrecy of a patent for a big European
Union Parliament Pow Wow on 'intellectual property' so called.

Thanks very much,
Laura Creighton


                 reply	other threads:[~2003-11-29 17:13 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200311291713.hATHDaQg029076@ratthing-b246.strakt.com \
    --to=lac@strakt.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).