From: Christoph Hellwig <hch@infradead.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Documentation <linux-doc@ger.kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Akira Yokosawa <akiyks@gmail.com>,
Stanislav Fomichev <sdf@google.com>,
David Vernet <void@manifault.com>,
Miguel Ojeda <ojeda@kernel.org>, James Seo <james@equiv.tech>,
Daniel Vetter <daniel.vetter@ffwll.ch>,
Federico Vaga <federico.vaga@vaga.pv.it>,
Carlos Bilbao <carlos.bilbao@amd.com>
Subject: Re: [PATCH RFC 0/4] Documentation: Web fonts for kernel documentation
Date: Fri, 3 Nov 2023 07:30:56 -0700 [thread overview]
Message-ID: <ZUUEIBx1txD8YQgU@infradead.org> (raw)
In-Reply-To: <20231102120053.30630-1-bagasdotme@gmail.com>
On Thu, Nov 02, 2023 at 07:00:42PM +0700, Bagas Sanjaya wrote:
> Intro
> =====
>
> The Linux kernel documentation is primarily composed of text (both
> prose and code snippets) and a few images. Hence, making the text
> easy to read by proper typography choices is crucial.
No, it's not. Not to the point where we need to ship a font with the
kernel tree for sure.
prev parent reply other threads:[~2023-11-03 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 12:00 [PATCH RFC 0/4] Documentation: Web fonts for kernel documentation Bagas Sanjaya
2023-11-02 12:00 ` [PATCH RFC 1/4] LICENSES: Add SIL Open Font License 1.1 Bagas Sanjaya
2023-11-02 14:06 ` Greg Kroah-Hartman
2023-11-03 8:11 ` Bagas Sanjaya
2023-11-03 8:49 ` Greg Kroah-Hartman
2023-11-04 0:53 ` Bagas Sanjaya
2023-11-04 9:52 ` Greg Kroah-Hartman
2023-11-05 23:40 ` Bagas Sanjaya
2023-11-02 14:09 ` Richard Fontana
2023-11-03 8:20 ` Bagas Sanjaya
2023-11-02 12:00 ` [PATCH RFC 2/4] Docmentation: Use IBM Plex Sans for page body Bagas Sanjaya
2023-11-02 12:00 ` [PATCH RFC 3/4] Documentation: Use Newsreader font for document headings Bagas Sanjaya
2023-11-02 12:00 ` [PATCH RFC 4/4] Documentation: Use IBM Plex Mono as monospace font Bagas Sanjaya
2023-11-02 12:17 ` [PATCH RFC 0/4] Documentation: Web fonts for kernel documentation Bagas Sanjaya
2023-11-02 16:41 ` Miguel Ojeda
2023-11-03 14:30 ` Christoph Hellwig [this message]
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=ZUUEIBx1txD8YQgU@infradead.org \
--to=hch@infradead.org \
--cc=akiyks@gmail.com \
--cc=bagasdotme@gmail.com \
--cc=carlos.bilbao@amd.com \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=federico.vaga@vaga.pv.it \
--cc=gregkh@linuxfoundation.org \
--cc=james@equiv.tech \
--cc=linux-doc@ger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojeda@kernel.org \
--cc=sdf@google.com \
--cc=tglx@linutronix.de \
--cc=void@manifault.com \
/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