From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@vger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Akira Yokosawa <akiyks@gmail.com>,
Stanislav Fomichev <sdf@google.com>,
David Vernet <void@manifault.com>,
Miguel Ojeda <ojeda@kernel.org>, James Seo <james@equiv.tech>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Carlos Bilbao <carlos.bilbao@amd.com>,
linux-spdx@vger.kernel.org, Richard Fontana <rfontana@redhat.com>
Subject: Re: [PATCH RFC RESEND 1/4] LICENSES: Add SIL Open Font License 1.1
Date: Thu, 2 Nov 2023 15:09:21 +0100 [thread overview]
Message-ID: <2023110211-absolute-backfire-b6a0@gregkh> (raw)
In-Reply-To: <20231102123225.32768-2-bagasdotme@gmail.com>
On Thu, Nov 02, 2023 at 07:32:19PM +0700, Bagas Sanjaya wrote:
> Add the license text along with appropriate tags for reference and
> tooling. The text is taken from the text as distributed in Google
> Fonts's zip files.
>
> As the license itself may or may note be compatible with GPLv2,
> let's take on the err side and require combining it with
> GPL-compatible licenses when using the license.
>
> Cc: linux-spdx@vger.kernel.org
> Cc: Richard Fontana <rfontana@redhat.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
> ---
> LICENSES/dual/OFL-1.1 | 107 ++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 107 insertions(+)
> create mode 100644 LICENSES/dual/OFL-1.1
Same comment as made before here:
https://lore.kernel.org/all/2023110222-renewed-monologue-008e@gregkh/
next prev parent reply other threads:[~2023-11-02 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231102123225.32768-1-bagasdotme@gmail.com>
2023-11-02 12:32 ` [PATCH RFC RESEND 1/4] LICENSES: Add SIL Open Font License 1.1 Bagas Sanjaya
2023-11-02 14:09 ` Greg Kroah-Hartman [this message]
2023-11-03 7:44 ` Bagas Sanjaya
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=2023110211-absolute-backfire-b6a0@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=federico.vaga@vaga.pv.it \
--cc=james@equiv.tech \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spdx@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=rfontana@redhat.com \
--cc=sdf@google.com \
--cc=tglx@linutronix.de \
--cc=void@manifault.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 read-only IMAP folder(s) and NNTP newsgroup(s).