Re: [PATCH] git-mktree: reverse of git-ls-tree.
- From
Andreas Ericsson <ae@op5.se>
- Date
- Feb 21, 2006, 08:46 UTC
- Message-ID
- <43FAD35E.5080401@op5.se>
- In-Reply-To
- <1140504750.16926.111.camel@evo.keithp.com>
Keith Packard wrote:
Show 19 quoted lines
> <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