From: Steve McKay <shubalubdub@gmail.com>
To: Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: Replace the extended ASCII copyright char to normal ASCII sequence
Date: Sat, 23 Jan 2010 12:44:40 -0600 [thread overview]
Message-ID: <ab644e481001231044r34651f25y7f7a98b1d76d4f93@mail.gmail.com> (raw)
In-Reply-To: <20100123090005.GA3897@brick.ozlabs.ibm.com>
On Sat, Jan 23, 2010 at 3:00 AM, Paul Mackerras <paulus@samba.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.
prev parent reply other threads:[~2010-01-23 18:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-22 10:25 Li Hong
2010-01-23 9:00 ` Paul Mackerras
2010-01-23 18:44 ` Steve McKay [this message]
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=ab644e481001231044r34651f25y7f7a98b1d76d4f93@mail.gmail.com \
--to=shubalubdub@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.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
all inboxes | Powered by JetHome®