From: Thomas Gleixner <tglx@linutronix.de>
To: Nishanth Menon <nm@ti.com>,
Thorsten Leemhuis <linux@leemhuis.info>,
Jonathan Corbet <corbet@lwn.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-spdx@vger.kernel.org,
Nishanth Menon <nm@ti.com>, 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, 07 Jul 2021 11:04:45 +0200 [thread overview]
Message-ID: <87eecaqytu.ffs@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20210703012931.30604-1-nm@ti.com>
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.
> Creative Commons is not a party to its public
> licenses. Notwithstanding, Creative Commons may elect to apply one of
> 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.
Acked-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2021-07-07 9:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-03 1:29 [PATCH] LICENSES/dual/CC-BY-4.0: Lets switch to utf-8 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 [this message]
2021-07-07 16:41 ` Pavel Machek
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=87eecaqytu.ffs@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).