From: "David Schwartz" <davids@webmaster.com>
To: "Jesse Pollard" <jesse@cats-chateau.net>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: Promise SATA driver GPL'd
Date: Thu, 24 Jul 2003 11:37:13 -0700 [thread overview]
Message-ID: <MDEHLPKNGKAHNMBLJOLKGELPEJAA.davids@webmaster.com> (raw)
In-Reply-To: <03072408233000.14335@tabby>
> On Wednesday 23 July 2003 19:21, David Schwartz wrote:
> > No matter how much code I write for which I don't give you
> > the source, the
> > amount of code for which you do have the source is not reduced. The more
> > free code there is, the freer you are. The only thing that
> > threatens your
> > freedom is if someone makes free code unfree. How do they do that?
> By claiming they wrote it first, supplying enough lawyers and
> court fees to
> put you out of existance.
Of course, that is certainly true. Someone can attempt, through the legal
process, to stop you from using software you yourself wrote. Although I
doubt any company would ever be that evil. ;)
That is, by the way, one advantage of taking a printout of your code and
mailing it to yourself in a sealed envelope or seeking a registered
copyright. It at least provides proof that you had the code on the date you
wrote it.
There is one other benefit to a registered copyright on software that a
lawyer recently mentioned to me. Suppose you're a company and have employees
who write software. You really can't be 100% sure that the software they
provide to you isn't stolen from someplace (and you sure as heck can't be
sure someone can't claim it is).
By seeking a registered copyright, you can argue that the registration
provides constructive notice to anyone else that you are claiming copyright
on that software. This *may* start the 3 year statue of limitations from the
date or registration rather than the date they found out you had software
they think is theirs.
DS
next prev parent reply other threads:[~2003-07-24 18:22 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:12 Adam J. Richter
2003-07-23 5:28 ` Andre Hedrick
2003-07-23 9:08 ` Adrian Bunk
2003-07-23 10:12 ` Matthias Andree
2003-07-23 10:21 ` Wichert Akkerman
2003-07-23 11:47 ` Alan Cox
2003-07-23 11:54 ` Wichert Akkerman
2003-07-23 22:22 ` On "any later version" in GPL [Was: Re: Promise SATA driver GPL'd] Horst von Brand
2003-07-23 10:37 ` Promise SATA driver GPL'd Adrian Bunk
2003-07-23 10:29 ` Alan Cox
2003-07-23 10:51 ` Adrian Bunk
2003-07-23 11:43 ` Alan Cox
2003-07-23 12:17 ` Adrian Bunk
2003-07-23 12:32 ` Martin Diehl
2003-07-23 12:57 ` Alan Cox
2003-07-23 19:08 ` Andre Hedrick
2003-07-23 19:19 ` Alan Cox
2003-07-23 19:33 ` Andre Hedrick
2003-07-23 19:46 ` Andre Hedrick
2003-07-23 20:59 ` Roman Zippel
2003-07-23 22:22 ` Andre Hedrick
2003-07-23 22:40 ` Roman Zippel
2003-07-23 22:35 ` Andre Hedrick
2003-07-23 23:02 ` Roman Zippel
2003-07-23 23:08 ` Andre Hedrick
2003-07-23 23:33 ` Roman Zippel
2003-07-23 23:45 ` Andre Hedrick
2003-07-24 0:14 ` dacin
2003-07-24 0:23 ` Andre Hedrick
2003-07-24 0:21 ` David Schwartz
2003-07-24 0:21 ` Andre Hedrick
2003-07-24 13:23 ` Jesse Pollard
2003-07-24 14:01 ` Richard B. Johnson
2003-07-24 18:37 ` David Schwartz [this message]
2003-07-23 22:32 ` Andre Hedrick
2003-07-23 22:46 ` Larry McVoy
2003-07-23 23:13 ` Roman Zippel
2003-07-23 10:40 ` Adam Sampson
-- strict thread matches above, loose matches on Subject: below --
2003-07-22 18:45 Erik Andersen
2003-07-22 18:54 ` Jeff Garzik
2003-07-22 19:07 ` Erik Andersen
2003-07-22 19:39 ` Samuel Flory
2003-07-22 20:56 ` Jeff Garzik
2003-07-22 21:39 ` Erik Andersen
2003-07-22 23:25 ` Jeff Garzik
2003-08-27 3:01 ` Nick Urbanik
2003-08-27 3:14 ` Jeff Garzik
2003-08-27 9:00 ` Matthias Andree
2003-08-27 11:51 ` Jeff Garzik
2003-07-22 20:57 ` Jeff Garzik
2003-07-23 13:20 ` Mark Watts
2003-07-23 1:59 ` Andre Hedrick
2003-07-23 2:38 ` Shawn
2003-07-23 10:32 ` Alan Cox
2003-07-23 18:58 ` Andre Hedrick
2003-07-24 11:22 ` Matthias Andree
2003-08-13 13:34 ` Vojtech Pavlik
2003-08-13 14:24 ` Jeff Garzik
2003-08-15 10:17 ` Andre Hedrick
2003-07-25 3:44 ` Milan Roubal
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=MDEHLPKNGKAHNMBLJOLKGELPEJAA.davids@webmaster.com \
--to=davids@webmaster.com \
--cc=jesse@cats-chateau.net \
--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
all inboxes | Powered by JetHome®