The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: Garrett LeSage <garrett@lesage.us>,
	IFo Hancroft <contact@ifohancroft.com>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Miguel Ojeda <ojeda@kernel.org>
Subject: Re: [PATCH v1 1/2] docs: move Linux logo into a new `images` folder
Date: Thu, 12 May 2022 09:37:35 -0600	[thread overview]
Message-ID: <87r14y4v9c.fsf@meer.lwn.net> (raw)
In-Reply-To: <20220510172530.29704-1-ojeda@kernel.org>

Miguel Ojeda <ojeda@kernel.org> writes:

> Having assets in the top-level `Documentation` directory can make
> it harder to find the documents one needs, especially if we want
> to add more of them later on.
>
> Instead, create a new `images` folder inside it that is used
> to hold assets such as logos.
>
> Link: https://lore.kernel.org/lkml/8735hicoy7.fsf@meer.lwn.net/
> Suggested-by: Jonathan Corbet <corbet@lwn.net>
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
> ---
>  Documentation/{ => images}/COPYING-logo |   0
>  Documentation/{ => images}/logo.gif     | Bin
>  2 files changed, 0 insertions(+), 0 deletions(-)
>  rename Documentation/{ => images}/COPYING-logo (100%)
>  rename Documentation/{ => images}/logo.gif (100%)
>
> diff --git a/Documentation/COPYING-logo b/Documentation/images/COPYING-logo
> similarity index 100%
> rename from Documentation/COPYING-logo
> rename to Documentation/images/COPYING-logo
> diff --git a/Documentation/logo.gif b/Documentation/images/logo.gif
> similarity index 100%
> rename from Documentation/logo.gif
> rename to Documentation/images/logo.gif

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.

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..:)

Thanks,

jon

  parent reply	other threads:[~2022-05-12 15:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10 17:25 [PATCH v1 1/2] docs: move Linux logo into a new `images` folder Miguel Ojeda
2022-05-10 17:25 ` [PATCH v1 2/2] docs: add SVG version of the Linux logo Miguel Ojeda
2022-05-12 15:37 ` Jonathan Corbet [this message]
2022-05-12 16:39   ` [PATCH v1 1/2] docs: move Linux logo into a new `images` folder 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=87r14y4v9c.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=contact@ifohancroft.com \
    --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