lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ab644e481001231044r34651f25y7f7a98b1d76d4f93@mail.gmail.com>
Date:	Sat, 23 Jan 2010 12:44:40 -0600
From:	Steve McKay <shubalubdub@...il.com>
To:	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf: Replace the extended ASCII copyright char to normal 
	ASCII sequence

On Sat, Jan 23, 2010 at 3:00 AM, Paul Mackerras <paulus@...ba.org> wrote:

> On Fri, Jan 22, 2010 at 06:25:41PM +0800, Li Hong wrote:
>
>> A copyright extended ASCII char (0xa9) in kernel/perf_event.c makes my utf-8
>> compatible vim think it is a binary file. It is better to either use a utf-8
>> sequence 0xc20xa9 or just normal copyright ASCII chars '(C)'.
>
> The trouble is, I've been informed that "(C)" has no legal meaning --
> it is not equivalent to the C-in-a-circle copyright symbol.  That's
> why I put the extended ASCII character in there.  I wouldn't mind the
> utf-8 sequence instead though.
>
> Paul.

>From the Copyright Law FAQ:

A proper copyright notice consists of three things: 1) the letter "C" in
a circle (called, logically enough, the "copyright symbol"), or the word
"Copyright," or the abbreviation "Copr."; 2) the year of first
publication; 3) the name of the copyright owner.  17 U.S.C. 401(b).

http://www.faqs.org/faqs/law/copyright/faq/part2/
http://www.copyright.gov/title17/92chap4.html

(C) and © appear to  be unnecessary if Copyright <year> <name> is
already present. IANAL, side effects may include, not intended to
diagnose, treat, or prevent, etc.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ