From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Andreas Ericsson" <ae@op5.se>,
git@vger.kernel.org, "Keith Packard" <keithp@keithp.com>
Subject: Re: [PATCH] git-mktree: reverse of git-ls-tree.
Date: Tue, 21 Feb 2006 23:20:40 +1300 [thread overview]
Message-ID: <46a038f90602210220w68edb71aq9f9f54ac278cb9e0@mail.gmail.com> (raw)
In-Reply-To: <7vr75x11or.fsf@assigned-by-dhcp.cox.net>
On 2/21/06, Junio C Hamano <junkio@cox.net> wrote:
> Keith is saying that unlike ciecle-c, (c) is meaningless. While
> he is right about that, it does not matter, as long as he is
> talking about "legal meaning in the US". It is my understanding
> that spelled out "Copyright" (or its abbreviation, "Copr.")
> weighs as much as the circle-c mark.
>
> And it matters even less these days. US law traditionally
> required copyright notice to be protected, but after 1989 US
> Copyright Act, made in line with Berne convention, the notice is
> not even necessary. It used to be that you would want circle-c,
> Copyright and "All Rights Reserved", if you really wanted to be
> anal. Buenos Aires signatories are all Berne members these
> days, it became just obsolete inertia.
Not entirely useless though. It serves as an indication of who to
contact for permission to copy. It's not as good as it should be
("which of the 35 L.Torvalds in the phonebook does this mean?").
Copyright law reform proponents do sometimes talk of a central
database with contact details for copyright owners and other measures
to facilitate brokerage of licenses.
It also serves as a reminder of the need for a license, though legally
it's not required. Just like a lock in the door, while often easy to
pick or crack open and definitely not required, reminds people that
trespassing is a crime.
Bah, social mores, laws and other vices of humanity...
martin
next prev parent reply other threads:[~2006-02-21 10:21 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 [this message]
2006-02-21 17:23 ` Keith Packard
2006-02-21 17:57 ` Linus Torvalds
2006-02-21 17:40 ` Linus Torvalds
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=46a038f90602210220w68edb71aq9f9f54ac278cb9e0@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=keithp@keithp.com \
/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).