From: Roman Zippel <zippel@linux-m68k.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: Tue, 28 May 2002 19:31:01 +0200 [thread overview]
Message-ID: <3CF3BED5.6E194618@linux-m68k.org> (raw)
In-Reply-To: <200205281612.g4SGC4t03662@localhost.localdomain>
Hi,
James Bottomley wrote:
> Actually, a patent does do exactly this. A patent gives you a "negative"
> right to exclude anyone from using your patented method or process. If you
> choose never to licence your patent (as is your right to do so) you block
> everyone else from making use of it.
Hmm, I didn't know that. I must have misunderstood something, I'm sorry
about that.
> In general, about the only restrictions on patents and their licensing
> arrangements in the US are the antitrust laws. See:
>
> http://www.usdoj.gov/atr/public/guidelines/ipguide.htm
>
> for a good guide from the horse's mouth.
Uh, that's quite a lot of lawyer language, something like this is
already difficult to understand in the native language. Could you point
me to the relevant section, I misunderstood? I couldn't find it.
bye, Roman
next prev parent reply other threads:[~2002-05-28 17:31 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 16:12 A reply on the RTLinux discussion James Bottomley
2002-05-28 17:31 ` Roman Zippel [this message]
2002-05-28 18:03 ` James Bottomley
2002-05-28 21:21 ` Jeff V. Merkey
2002-05-29 8:58 ` Peter Wächtler
-- strict thread matches above, loose matches on Subject: below --
2002-05-29 12:36 Rose, Billy
2002-05-29 19:46 ` Daniel Phillips
2002-05-29 19:58 ` Mark Mielke
[not found] <57.c083d0f.2a237c49@aol.com>
2002-05-27 12:36 ` RTAI/RtLinux Wolfgang Denk
2002-05-28 12:04 ` A reply on the RTLinux discussion yodaiken
2002-05-28 14:37 ` Roman Zippel
2002-05-28 15:57 ` Alan Cox
2002-05-28 15:11 ` Roman Zippel
2002-05-28 16:45 ` Alan Cox
2002-05-29 0:31 ` Roman Zippel
2002-05-29 1:34 ` Mark Mielke
2002-05-29 3:11 ` Karim Yaghmour
2002-05-29 8:53 ` Zwane Mwaikambo
2002-05-29 13:54 ` Dana Lacoste
2002-05-29 15:17 ` Alan Cox
2002-05-29 14:20 ` Dana Lacoste
2002-05-29 15:15 ` Mark Mielke
2002-05-29 17:43 ` Dana Lacoste
2002-05-29 18:26 ` Mark Mielke
2002-05-29 15:31 ` Alan Cox
2002-05-29 15:45 ` yodaiken
2002-05-29 17:40 ` Dana Lacoste
2002-06-03 10:09 ` Rob Landley
2002-05-29 13:24 ` Alan Cox
2002-05-29 13:43 ` Roman Zippel
2002-05-29 14:59 ` Alan Cox
2002-05-29 20:18 ` Roman Zippel
2002-05-31 11:57 ` Pavel Machek
2002-05-31 21:34 ` Mark Mielke
2002-05-31 23:19 ` yodaiken
2002-05-28 15:19 ` Karim Yaghmour
2002-05-28 15:39 ` Mark Mielke
2002-05-28 16:00 ` Karim Yaghmour
2002-06-01 20:37 ` Michael Barabanov
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=3CF3BED5.6E194618@linux-m68k.org \
--to=zippel@linux-m68k.org \
--cc=James.Bottomley@steeleye.com \
--cc=linux-kernel@vger.kernel.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