Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Message-ID: <135d2b02-a888-f3ae-ee16-ef30ab80e529@gmail.com>
Date:   Sun, 29 May 2022 07:24:00 +0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.9.1
Subject: Re: [PATCH v2 1/2] docs: move Linux logo into a new `images` folder
Content-Language: en-US
To:     Miguel Ojeda <ojeda@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc:     Garrett LeSage <garrett@lesage.us>,
        IFo Hancroft <contact@ifohancroft.com>,
        linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
References: <20220528153132.8636-1-ojeda@kernel.org>
From:   Bagas Sanjaya <bagasdotme@gmail.com>
In-Reply-To: <20220528153132.8636-1-ojeda@kernel.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk

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/.

-- 
An old man doll... just what I always wanted! - Clara