From: Bagas Sanjaya <bagasdotme@gmail.com>
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
Subject: Re: [PATCH v2 1/2] docs: move Linux logo into a new `images` folder
Date: Sun, 29 May 2022 07:24:00 +0700 [thread overview]
Message-ID: <135d2b02-a888-f3ae-ee16-ef30ab80e529@gmail.com> (raw)
In-Reply-To: <20220528153132.8636-1-ojeda@kernel.org>
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
next prev parent reply other threads:[~2022-05-29 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 15:31 [PATCH v2 1/2] docs: move Linux logo into a new `images` folder Miguel Ojeda
2022-05-29 0:24 ` Bagas Sanjaya [this message]
2022-05-29 14:27 ` Jonathan Corbet
2022-06-01 15:33 ` Jonathan Corbet
[not found] ` <20220528153132.8636-2-ojeda@kernel.org>
2022-06-02 7:39 ` [PATCH v2 2/2] docs: add SVG version of the Linux logo Geert Uytterhoeven
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=135d2b02-a888-f3ae-ee16-ef30ab80e529@gmail.com \
--to=bagasdotme@gmail.com \
--cc=contact@ifohancroft.com \
--cc=corbet@lwn.net \
--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;
as well as URLs for NNTP newsgroup(s).