From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: 69429@debbugs.gnu.org
Cc: "Hilton Chain" <hako@ultrarare.space>,
"Zhu Zihao" <all_but_last@163.com>, 宋文武 <iyzsong@envs.net>
Subject: [bug#69429] [PATCH v2 0/3] Update Chiron fonts and split outputs.
Date: Wed, 28 Feb 2024 11:20:40 +0800 [thread overview]
Message-ID: <cover.1709090139.git.hako@ultrarare.space> (raw)
In-Reply-To: <cover.1709046857.git.hako@ultrarare.space>
V1->V2: Simplify phases.
Hilton Chain (3):
gnu: font-chiron-sung-hk: Update to 1.011.
gnu: font-chiron-hei-hk: Update to 2.509.
gnu: font-chiron-sung-hk: Split outputs.
gnu/packages/fonts.scm | 22 ++++++++++++++++++----
1 file changed, 18 insertions(+), 4 deletions(-)
base-commit: 8c0282cf543fe205a5b89201cd7bb8889121a07c
--
2.41.0
next prev parent reply other threads:[~2024-02-28 3:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 15:25 [bug#69429] [PATCH 0/3] Update Chiron fonts and split outputs Hilton Chain via Guix-patches via
2024-02-27 15:58 ` [bug#69429] [PATCH 1/3] gnu: font-chiron-sung-hk: Update to 1.011 Hilton Chain via Guix-patches via
2024-02-27 15:58 ` [bug#69429] [PATCH 2/3] gnu: font-chiron-hei-hk: Update to 2.509 Hilton Chain via Guix-patches via
2024-02-27 15:58 ` [bug#69429] [PATCH 3/3] gnu: font-chiron-sung-hk: Split outputs Hilton Chain via Guix-patches via
2024-02-28 3:20 ` Hilton Chain via Guix-patches via [this message]
2024-02-28 3:27 ` [bug#69429] [PATCH v2 1/3] gnu: font-chiron-sung-hk: Update to 1.011 Hilton Chain via Guix-patches via
2024-02-28 3:27 ` [bug#69429] [PATCH v2 2/3] gnu: font-chiron-hei-hk: Update to 2.509 Hilton Chain via Guix-patches via
2024-02-28 3:27 ` [bug#69429] [PATCH v2 3/3] gnu: font-chiron-sung-hk: Split outputs Hilton Chain via Guix-patches via
2024-03-07 10:30 ` [bug#69429] [PATCH v2 0/3] Update Chiron fonts and split outputs 宋文武 via Guix-patches via
2024-03-09 3:18 ` bug#69429: " Hilton Chain via Guix-patches via
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1709090139.git.hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=69429@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=hako@ultrarare.space \
--cc=iyzsong@envs.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).