From: Linus Torvalds <torvalds@osdl.org>
To: Keith Packard <keithp@keithp.com>
Cc: Junio C Hamano <junkio@cox.net>, Tommi Virtanen <tv@debian.org>,
git@vger.kernel.org
Subject: Re: [PATCH] git-mktree: reverse of git-ls-tree.
Date: Tue, 21 Feb 2006 09:40:06 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602210915320.30245@g5.osdl.org> (raw)
In-Reply-To: <1140504750.16926.111.camel@evo.keithp.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2509 bytes --]
On Mon, 20 Feb 2006, Keith Packard wrote:
>
> > + * Copyright (c) Junio C Hamano, 2006
>
> I've been told by at least two lawyers that the string '(c)' has no
> legal meaning in the US. If you want to indicate copyright, the only
> symbol which does carry legal weight is the c-in-a-circle mark '©'.
You should change lawyers, methinks.
The thing is, once the same line says "Copyright", the string '(c)' may be
meaningless, but more importantly, your lawyers are wasting your time with
pointless and mindless "punktknulleri" (literal meaning: "the f*cking of
points", aka being anal retentive).
Of course, they are probably also charging you for that time they are
wasting, which is why you should fire them and find somebody who tells you
anything relevant.
The FACT is that
(a) You can write out the word "copyright" in its entirety.
(b) the US legal system very much takes intent into account, so even if
you don't, if the meaning is clear, it's not like it matters. This
is even more true on most of the rest of the civilized world, btw (ie
Europe in general gives authors _more_ rights than the US, since they
recognize the notion of "moral rights")
(c) you own the copyright anyway ever since 1988, when the US ratified
the Berne convention. In fact, even before then, the US had adopted
the notion of automatic copyrights, and any work created after 1978
falls under this.
Anyway, for more details if you _really_ care, look up "Circular 3" by the
United States Copyright Office. The very first sentence of that paper
talks about how the notice isn't even required any more, but if you want
to talk to your punktknullande lawyers, point them to the section called
"form of notice". Which mentions the © letter, but makes it very very
clear that "Copyright" or the abbreviation "Copr." are totally
interchangeable in the US.
Now, in some _other_ countries, the © mark may be special, but quite
frankly, you won't really care. If it matters, those countries haven't
ratified the Berne convention, and you'll never ever in a million years
care about them. It's absolutely certainly not the case in any relevant
country.
Any country where "©" matters likely has many bigger problems wrt
copyrights, like not honoring them at all.
So: if you care about the copyright law in Ulan Bator, you may have to use
the © character. But the likelihood is that it's not an issue even there.
So tell your lawyers to f*ck the hell off.
Linus
next prev parent reply other threads:[~2006-02-21 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-21 6:37 [PATCH] git-mktree: reverse of git-ls-tree Junio C Hamano
2006-02-21 6:52 ` Keith Packard
2006-02-21 8:46 ` Andreas Ericsson
2006-02-21 9:49 ` Junio C Hamano
2006-02-21 10:20 ` Martin Langhoff
2006-02-21 17:23 ` Keith Packard
2006-02-21 17:57 ` Linus Torvalds
2006-02-21 17:40 ` Linus Torvalds [this message]
2006-02-21 17:46 ` Keith Packard
2006-02-21 18:00 ` Linus Torvalds
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=Pine.LNX.4.64.0602210915320.30245@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=keithp@keithp.com \
--cc=tv@debian.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;
as well as URLs for NNTP newsgroup(s).