From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: gsettings-desktop-schemas: missing font dependency
Date: Wed, 31 Jan 2024 19:20:28 +0100 [thread overview]
Message-ID: <20240131182028.E74B329E55@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48382@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 521 bytes --]
New comment by ahesford on void-packages repository
https://github.com/void-linux/void-packages/pull/48382#issuecomment-1919672433
Comment:
My argument is that upstream should use a generic label, not necessarily that we should patch the schema. The reference to Cantarell may be considered a special case because the font is maintained by the GNOME project as the official UI font, whereas Source Code Pro is an external font whose associated use in terminal emulators is likely to incite a lot of passionate opinion.
next prev parent reply other threads:[~2024-01-31 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 16:27 [PR PATCH] " c0m4r
2024-01-31 16:09 ` ahesford
2024-01-31 17:11 ` c0m4r
2024-01-31 17:14 ` c0m4r
2024-01-31 18:20 ` ahesford [this message]
2024-01-31 19:39 ` c0m4r
2024-02-02 7:38 ` [PR PATCH] [Closed]: " c0m4r
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=20240131182028.E74B329E55@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).