Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
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
In-Reply-To: <135d2b02-a888-f3ae-ee16-ef30ab80e529@gmail.com>
References: <20220528153132.8636-1-ojeda@kernel.org>
 <135d2b02-a888-f3ae-ee16-ef30ab80e529@gmail.com>
Date:   Sun, 29 May 2022 08:27:51 -0600
Message-ID: <8735gs9zx4.fsf@meer.lwn.net>
MIME-Version: 1.0
Content-Type: text/plain
Precedence: bulk

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