lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <135d2b02-a888-f3ae-ee16-ef30ab80e529@gmail.com>
Date:   Sun, 29 May 2022 07:24:00 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Miguel Ojeda <ojeda@...nel.org>, Jonathan Corbet <corbet@....net>
Cc:     Garrett LeSage <garrett@...age.us>,
        IFo Hancroft <contact@...hancroft.com>,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] docs: move Linux logo into a new `images` folder

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ