linux-spdx.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Nishanth Menon <nm@ti.com>,
	Thorsten Leemhuis <linux@leemhuis.info>,
	Jonathan Corbet <corbet@lwn.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>, Rahul T R <r-ravikumar@ti.com>
Subject: Re: [PATCH] LICENSES/dual/CC-BY-4.0: Lets switch to utf-8
Date: Wed, 7 Jul 2021 18:41:48 +0200	[thread overview]
Message-ID: <20210707164148.GA5380@localhost> (raw)
In-Reply-To: <87eecaqytu.ffs@nanos.tec.linutronix.de>

On Wed 2021-07-07 11:04:45, Thomas Gleixner wrote:
> Nishanth,
> 
> On Fri, Jul 02 2021 at 20:29, Nishanth Menon wrote:
> > Lets drop the unicode characters that peeped in and replace with
> 
> Again: s/Lets// 
> 
> > equivalent utf-8 characters. This makes the CC-BY-4.0 file inline with
> > rest of license files.

s/utf-8/ASCII/? otherwise the description makes no sense...

> >  its public licenses to material it publishes and in those instances
> > -will be considered the “Licensor.” The text of the Creative Commons
> > +will be considered the "Licensor." The text of the Creative Commons
> 
> In theory the License text should be a verbatim copy. But yes, this
> unicode stuff is a pain.

But we use unicode elsewhere for random stuff, and license should
be verbatim, so I'm not sure this is good idea.

			      		  	   Pavel
						   
-- 

  reply	other threads:[~2021-07-07 16:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-03  1:29 Nishanth Menon
2021-07-03  1:34 ` Randy Dunlap
2021-07-05 15:08 ` Jonathan Corbet
2021-07-06  6:59   ` Thorsten Leemhuis
2021-07-06 12:48   ` Nishanth Menon
2021-07-07  9:04 ` Thomas Gleixner
2021-07-07 16:41   ` Pavel Machek [this message]
2021-07-12 16:03 ` Jonathan Corbet

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=20210707164148.GA5380@localhost \
    --to=pavel@ucw.cz \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spdx@vger.kernel.org \
    --cc=linux@leemhuis.info \
    --cc=nm@ti.com \
    --cc=r-ravikumar@ti.com \
    --cc=tglx@linutronix.de \
    --subject='Re: [PATCH] LICENSES/dual/CC-BY-4.0: Lets switch to utf-8' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).