linux-kernel - Re: [PATCH v1 1/2] docs: move Linux logo into a new `images` folder

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 12 May 2022 18:39:07 +0200
From:   Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To:     Jonathan Corbet <corbet@....net>
Cc:     Miguel Ojeda <ojeda@...nel.org>,
        Garrett LeSage <garrett@...age.us>,
        IFo Hancroft <contact@...hancroft.com>,
        Linux Doc Mailing List <linux-doc@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 1/2] docs: move Linux logo into a new `images` folder

On Thu, May 12, 2022 at 5:37 PM Jonathan Corbet <corbet@....net> wrote:
>
> This will break scripts/spdxcheck-test.sh - which somebody might
> actually try to run one of these years.  So this patch really needs to
> update that script to follow the move.

Ah, yes, my bad, will fix.

> As far as I can tell, that's the only reference to logo.gif in the
> entire tree.  It makes me wonder if we need it at all.  Digging through
> the history suggests it was added in 2.1.15, but never really used for
> anything.  It's only role would appear to be to serve as testing
> material for the SPDX checker..:)

If you mean removing the GIF one to replace it with the vector one, I
can send it that way too.

If you mean removing the logo from the tree, then I think it would be
useful to have it available in some other stable URL (so that people
can still fetch it for other purposes), e.g. at kernel.org (not sure
if there is such a place; in both kernel.org and LF's pages there is
just a mention). One potential use case for the logo is to use it
instead of the Rust logo in the Rust docs if the Rust support gets
merged (i.e. instead of the custom one).

At least I hope the Tasmanian devil got a bit of help thanks to the logo! :)

Cheers,
Miguel