docs: move Linux logo into a new `images` folder
Subsystems (2)
PATCH v2 1/2 docs: move Linux logo into a new `images` folder
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.
In addition, update the reference in scripts/spdxcheck-test.sh.
---
v1: https://lore.kernel.org/lkml/[email protected]/
v2:
- Added the scripts/spdxcheck-test.sh reference update, as noticed by Jonathan Corbet.
Documentation/{ => images}/COPYING-logo | 0
Documentation/{ => images}/logo.gif | Bin
scripts/spdxcheck-test.sh | 2 +-
3 files changed, 1 insertion(+), 1 deletion(-)
rename Documentation/{ => images}/COPYING-logo (100%)
rename Documentation/{ => images}/logo.gif (100%)Documentation/images/COPYING-logo renamed from Documentation/COPYING-logo +0 -0
Documentation/images/logo.gif renamed from Documentation/logo.gif +0 -0
scripts/spdxcheck-test.sh +1 -1
@@ -1,7 +1,7 @@ #!/bin/sh # run check on a text and a binary file -for FILE in Makefile Documentation/logo.gif; do +for FILE in Makefile Documentation/images/logo.gif; do python3 scripts/spdxcheck.py $FILE python3 scripts/spdxcheck.py - < $FILE done
base-commit: 4b0986a3613c92f4ec1bdc7f60ec66fea135991f
Signature · 1 line
2.36.1
PATCH v2 2/2 docs: add SVG version of the Linux logo
In the Rust for Linux patch series, Jonathan Corbet requested [1] that we avoid binary assets (such as the logo), possibly by recreating them in SVG format.
However, it turns out there is no SVG version of the Linux logo in the kernel tree yet, only a GIF one from the pre-v2.0.0 days.
This patch fixes that by adding a SVG version of the Linux logo, which we could then use in the Rust for Linux documentation and other similar places.
This is a vector re-illustration by Garrett LeSage of the original logo by Larry Ewing, plus cleanups by IFo Hancroft.
The file was imported as-is from:
https://github.com/garrett/Tux/blob/ecd40de64250ea2b24c849e901c3297ad01e54f6/tux.svg
The stated license in the repository is:
Quoted 7 lines
Public domain http://creativecommons.org/publicdomain/zero/1.0/
...but, if anyone asks:
Tux was originally made by Larry Ewing in the Gimp, re-illustrated in vector by Garrett LeSage, using Inkscape and refined and cleaned up by IFo Hancroft.
Here, the acknowledgement requirement has been made mandatory to match the wording of the existing GIF logo in COPYING-logo.
Both Garrett LeSage and IFo Hancroft gave their permission [2,3] to use their re-illustration with the license as given in the COPYING-logo file.
---
v1: https://lore.kernel.org/lkml/[email protected]/
v2:
- Added numeric citations [N] to links.
- Reworded commit message a bit.
Documentation/images/COPYING-logo | 8 + Documentation/images/logo.svg | 2040 +++++++++++++++++++++++++++++ 2 files changed, 2048 insertions(+) create mode 100644 Documentation/images/logo.svg
Documentation/images/COPYING-logo +8 -0
@@ -11,3 +11,11 @@ Larry's web-page: https://www.isc.tamu.edu/~lewing/linux/ +The SVG version was re-illustrated in vector by Garrett LeSage and +refined and cleaned up by IFo Hancroft. It is also freely usable +as long as you acknowledge Larry, Garrett and IFo as above. + +There are also black-and-white and inverted vector versions at +Garrett's repository: + + https://github.com/garrett/Tux
Documentation/images/logo.svg new file +2040 -0
2,040 lines not on this page · raw message
Signature · 1 line
2.36.1
Re: [PATCH v2 2/2] docs: add SVG version of the Linux logo
Hi Miguel,
Quoted 10 lines · Miguel Ojeda
In the Rust for Linux patch series, Jonathan Corbet requested [1] that we avoid binary assets (such as the logo), possibly by recreating them in SVG format.
However, it turns out there is no SVG version of the Linux logo in the kernel tree yet, only a GIF one from the pre-v2.0.0 days.
This patch fixes that by adding a SVG version of the Linux logo, which we could then use in the Rust for Linux documentation and other similar places.
Perhaps you want to add a Rust logo to drivers/video/logo/, to be shown using fb_append_extra_logo() when Rust technology is included?
;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 7 lines · Miguel Ojeda
Having assets in the top-level
Documentationdirectory 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
imagesfolder 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/.
Signature · 1 line
An old man doll... just what I always wanted! - Clara
Jonathan Corbet
maintainerQuoted 5 lines · Bagas Sanjaya
Quoted 4 lines · Miguel Ojeda
Having assets in the top-level
Documentationdirectory can make it harder to find the documents one needs, especially if we want to add more of them later on.
Quoted 8 lines
Quoted 3 lines
Instead, create a new
imagesfolder 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
Jonathan Corbet
maintainerQuoted 6 lines · Miguel Ojeda
Having assets in the top-level
Documentationdirectory 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
imagesfolder inside it that is used to hold assets such as logos.
Both patches applied, thanks.
jon