linux-kernel - Re: [PATCH] trivial: use (C) instead of \251

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: <20100501003410.GB2610@brick.ozlabs.ibm.com>
Date:	Sat, 1 May 2010 10:34:10 +1000
From:	Paul Mackerras <paulus@...ba.org>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Ingo Molnar <mingo@...e.hu>, Tejun Heo <tj@...nel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Paul Mackerras <paulus@....ibm.com>
Subject: Re: [PATCH] trivial: use (C) instead of \251

On Fri, Apr 30, 2010 at 11:04:46AM +0200, Jiri Kosina wrote:
> On Fri, 30 Apr 2010, Ingo Molnar wrote:
> 
> > > Well, Paul himself stated that according to their lawyer department, 
> > > "Copyright" (which is there) is enough. So it made sense to remove invalid 
> > > (at least in some sense) character.
> > > 
> > > Also zillion of other files copyrighted by Paul contain "Copyright (C)".
> > > 
> > > If we really want this character there then, why not rather in UTF-8, so 
> > > that it works flawlessly?
> > 
> > It might be fine but i havent seen Paul reply to this thread - and this is my 
> > point: _you_ should have waited for an ack from Paul (who is co-maintaining 
> > that file) before applying it. The commit doesnt have it:
> 
> I got Pauls reply as "as soon as there is `Copyright', it's fine". If I 
> misunderstood it, sorry for that, and I'll drop the patch.
> 
> Paul, could you please send explicit Acked-by: or Naked-by:, so that 
> everything is in line?

Nacked-by: Paul Mackerras <paulus@...ba.org>

Please apply the patch I just sent that changes the encoding to
UTF-8.

I take your point that there are lots of other copyright notices in
the kernel with "(C)", including mine, and I'm not for a moment
suggesting that they are all invalid.  Nevertheless, it seems that it
is better to use the proper copyright symbol rather than "(C)" for new
code, so I'd like to keep the copyright symbol here.

Paul.
--
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/