From: Itai Nahshon <nahshon@actcom.co.il>
To: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>,
pgallen@randomlogic.com, KPLUG List <kplug-list@kernel-panic.org>,
KPLUG Newbie <kplug-newbie@kernel-panic.org>,
KPLUG LPSG <kplug-lpsg@kernel-panic.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: SSSCA Hits the Senate
Date: Mon, 25 Mar 2002 19:34:08 +0200 [thread overview]
Message-ID: <200203251734.g2PHYLq24629@lmail.actcom.co.il> (raw)
In-Reply-To: <200203251522.JAA62284@tomcat.admin.navo.hpc.mil>
On Monday 25 March 2002 17:22, Jesse Pollard wrote:
> Has there been anything that says the copy protection code can't be source?
> If it were included in the source, along with all the other code, would
> that be recognized as "protected"?
Worst thing happens if somebody gets a patent for the copy protection schemes...
-- Itai
next prev parent reply other threads:[~2002-03-25 17:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 15:22 Jesse Pollard
2002-03-25 16:06 ` Ron Pagani / San Francisco / San Jose, CA
2002-03-25 16:09 ` Herman Oosthuysen
2002-03-25 22:33 ` Florian Weimer
2002-03-26 0:19 ` Thunder from the hill
2002-03-26 2:44 ` Stephen Samuel
2002-03-26 12:18 ` Thunder from the hill
2002-03-26 20:32 ` CBDTPA (Re: SSSCA Hits the Senate) son of SSSCA Andre Hedrick
2002-03-25 17:34 ` Itai Nahshon [this message]
2002-03-25 18:17 ` SSSCA Hits the Senate Alan Cox
2002-03-25 19:37 ` Herman Oosthuysen
2002-03-25 20:37 ` Rik van Riel
2002-03-25 21:24 ` Herman Oosthuysen
2002-03-25 22:43 ` Itai Nahshon
2002-03-26 0:25 ` Thunder from the hill
2002-03-25 21:29 ` Matthew D. Pitts
2002-03-26 20:30 ` Matt Reppert
2002-03-25 22:35 ` Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2002-03-25 20:58 Dieter Nützel
2002-03-25 21:33 ` Herman Oosthuysen
2002-03-25 17:50 Gabriel Sechan
2002-03-23 1:09 Paul G. Allen
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=200203251734.g2PHYLq24629@lmail.actcom.co.il \
--to=nahshon@actcom.co.il \
--cc=kplug-list@kernel-panic.org \
--cc=kplug-lpsg@kernel-panic.org \
--cc=kplug-newbie@kernel-panic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pgallen@randomlogic.com \
--cc=pollard@tomcat.admin.navo.hpc.mil \
/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
all inboxes | Powered by JetHome®