mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>, 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
Subject: Re: [PATCH v2 1/2] docs: move Linux logo into a new `images` folder
Date: Sun, 29 May 2022 08:27:51 -0600	[thread overview]
Message-ID: <8735gs9zx4.fsf@meer.lwn.net> (raw)
In-Reply-To: <135d2b02-a888-f3ae-ee16-ef30ab80e529@gmail.com>

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> On 5/28/22 22:31, Miguel Ojeda wrote:
>> 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.
>> 
>
> Do assets include CSS and JS files?
>
> And if we plan to add non-image assets to images/, that directory will
> be misleading. I suggest to name the directory as assets/.

Can you please point out any CSS or JavaScript files in the kernel tree,
or any that we might expect to have there anytime soon?  I don't think
this is a case we need to be worried about.

Thanks,

jon

  reply	other threads:[~2022-05-29 14:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-28 15:31 Miguel Ojeda
2022-05-28 15:31 ` [PATCH v2 2/2] docs: add SVG version of the Linux logo Miguel Ojeda
2022-06-02  7:39   ` Geert Uytterhoeven
2022-05-29  0:24 ` [PATCH v2 1/2] docs: move Linux logo into a new `images` folder Bagas Sanjaya
2022-05-29 14:27   ` Jonathan Corbet [this message]
2022-06-01 15:33 ` 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=8735gs9zx4.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --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
all inboxes | Powered by JetHome®