From: IFo Hancroft <contact@ifohancroft.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Garrett LeSage <garrett@lesage.us>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: add SVG version of Linux logo
Date: Mon, 7 Feb 2022 21:15:04 +0200 [thread overview]
Message-ID: <YgFvuIa0n3e6+cbq@battlestation> (raw)
In-Reply-To: <20220207014418.GA28724@kernel.org>
Hi,
You have my permission to use the vector version of Tux with the license given in the patch.
Best Regards,
IFo Hancroft
On Mon, Feb 07, 2022 at 02:44:18AM +0100, Miguel Ojeda wrote:
>In the Rust for Linux patch series, Jonathan Corbet requested that
>we avoid binary assets (logo and favicons for the generated
>documentation), possibly by recreating the logo in SVG format.
>
>However, it turns out there is no SVG version of the Linux logo
>in the kernel tree yet, only a GIF one from the pre-v2.0.0 days.
>Thus this commit fixes that, which then we can use in the Rust
>documentation in one way or another.
>
>This is a vector re-illustration by Garrett LeSage of the original
>logo by Larry Ewing (plus cleanups by IFo Hancroft). Garrett gave
>me (privately) his permission to use it for this purpose. The
>acknowledgement requirement has been made mandatory here to match
>the wording of the existing one.
>
>Link: https://lore.kernel.org/lkml/87fspk1xoc.fsf@meer.lwn.net/
>Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
>---
>Garrett, it would be great if you could confirm here that you
>are OK with the note in `COPYING-logo`. In particular, in your
>repository, you license the logo as public domain, though here
>I followed the existing licence which requires giving credit.
>Please see below.
>
> Documentation/COPYING-logo | 8 +
> Documentation/logo.svg | 2040 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 2048 insertions(+)
> create mode 100644 Documentation/logo.svg
>
>diff --git a/Documentation/COPYING-logo b/Documentation/COPYING-logo
>index b21c7cf7d9f6..fd7c9451fc72 100644
>--- a/Documentation/COPYING-logo
>+++ b/Documentation/COPYING-logo
>@@ -11,3 +11,11 @@ Larry's web-page:
>
> https://www.isc.tamu.edu/~lewing/linux/
>
>+The SVG version was re-illustrated in vector by Garrett LeSage and
>+refined and cleaned up by IFo Hancroft. It is also freely usable
>+as long as you acknowledge Larry, Garrett and IFo Hancroft as above.
>+
>+There are also black-and-white and inverted vector versions at
>+Garrett's repository:
>+
>+ https://github.com/garrett/Tux
next parent reply other threads:[~2022-02-07 19:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220207014418.GA28724@kernel.org>
2022-02-07 19:15 ` IFo Hancroft [this message]
2022-02-08 17:16 ` [PATCH] docs: add SVG version of Linux logo Garrett LeSage
2022-03-17 7:56 ` Miguel Ojeda
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=YgFvuIa0n3e6+cbq@battlestation \
--to=contact@ifohancroft.com \
--cc=corbet@lwn.net \
--cc=garrett@lesage.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@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