From: Paul Mackerras <paulus@samba.org>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Ingo Molnar <mingo@elte.hu>, Tejun Heo <tj@kernel.org>,
lkml <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@au1.ibm.com>
Subject: Re: [PATCH] trivial: use (C) instead of \251
Date: Sat, 1 May 2010 10:34:10 +1000 [thread overview]
Message-ID: <20100501003410.GB2610@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1004301103280.9849@pobox.suse.cz>
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@samba.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.
prev parent reply other threads:[~2010-05-01 0:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-28 9:30 Tejun Heo
2010-04-28 18:42 ` Harald Arnesen
2010-04-28 20:20 ` Tejun Heo
2010-04-29 10:34 ` Harald Arnesen
2010-04-28 21:55 ` Paul Mackerras
2010-04-29 5:32 ` Tejun Heo
2010-04-28 22:41 ` Jiri Kosina
2010-04-29 4:57 ` Paul Mackerras
2010-04-29 5:35 ` Tejun Heo
2010-04-30 7:55 ` Ingo Molnar
2010-04-30 7:59 ` Tejun Heo
2010-04-30 22:18 ` H. Peter Anvin
2010-04-30 8:01 ` Jiri Kosina
2010-04-30 8:37 ` Ingo Molnar
2010-04-30 9:04 ` Jiri Kosina
2010-04-30 9:28 ` Ingo Molnar
2010-05-01 0:34 ` Paul Mackerras [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=20100501003410.GB2610@brick.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@au1.ibm.com \
--cc=tj@kernel.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®