From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org
Subject: Re: A reply on the RTLinux discussion.
Date: Wed, 29 May 2002 10:58:37 +0200 [thread overview]
Message-ID: <3CF4983D.2080207@loewe-komp.de> (raw)
In-Reply-To: <zippel@linux-m68k.org> <200205281803.g4SI3vx05013@localhost.localdomain> <20020528142147.A7353@vger.timpanogas.org>
Jeff V. Merkey wrote:
>
> I've been reading all this discussion, and I think the solution
> is pretty simple. Patents are fairly easy to invalidate if you
> can show prior art. Novell and these big software companies
> do it all the time. When they implement something that infringes
> someone's patent, they wait until litigation is filed, then seek to
> invalidate specific claims in the patent. There are administrative
> procedures in place wih the USPTO that take this into account. It's
> expensive and you have to be willing to risk litigation.
>
Yes, exactly. Look at http://www.bountyquest.com
A patent gives the owner of the patent the right to _deny_ anybody
to use this "invention" (17 years when granted).
History has proved that inventions where done independantly in
different countries at almost the same time.
With software patents the chance that two programmers code something
up almost exactly the same way grows _rapidly_.
I don't like the fact, that somebody can deny me the use of my
own ideas. The whole idea of helping innovations with patents
is outdated.
next prev parent reply other threads:[~2002-05-29 8:57 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
2002-05-28 18:03 ` James Bottomley
2002-05-28 21:21 ` Jeff V. Merkey
2002-05-29 8:58 ` Peter Wächtler [this message]
-- 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=3CF4983D.2080207@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=James.Bottomley@SteelEye.com \
--cc=jmerkey@vger.timpanogas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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