git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
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:46:22 +0100	[thread overview]
Message-ID: <43FAD35E.5080401@op5.se> (raw)
In-Reply-To: <1140504750.16926.111.camel@evo.keithp.com>

Keith Packard wrote:
> <internationalization-pedant-mode>
> On Mon, 2006-02-20 at 22:37 -0800, Junio C Hamano 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 '©'. 
> 
> Of course, this does force the issue of what encoding to present source
> files in. I suggest that sources should be UTF-8, which also provides
> opportunities to encode author names correctly, rather than
> transliterating them to Latin. X.org uses UTF-8 for source files now
> without difficulty across a wide range of compilers. Of course,
> non-ascii glyphs are present only in comments.
> 
> </internationalization-pedant-mode>


In most countries the copyright is implied unless explicitly void by the 
author.

In other sane countries (I don't argue that USA is necessarily any such 
country), the law is such that if the copier understands that there is a 
copyright and violates it, he or she is in error and thus liable.

I'm not sure how mad such a law can be written, but what you describe go 
against both common sense and common practice since it puts the burden 
of protection on the victim-to-be before the crime is even committed. It 
would be like a rapist being let off because his victims were where he 
happened to be.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2006-02-21  8:46 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 [this message]
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
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=43FAD35E.5080401@op5.se \
    --to=ae@op5.se \
    --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).