From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: 宋文武 <iyzsong@envs.net>
Cc: 69429-done@debbugs.gnu.org, Zhu Zihao <all_but_last@163.com>
Subject: bug#69429: [PATCH v2 0/3] Update Chiron fonts and split outputs.
Date: Sat, 09 Mar 2024 11:18:27 +0800 [thread overview]
Message-ID: <8734t0t7ng.wl-hako@ultrarare.space> (raw)
In-Reply-To: <877cies5a3.fsf@envs.net>
Hi,
On Thu, 07 Mar 2024 18:30:28 +0800,
宋文武 wrote:
>
> Hilton Chain <hako@ultrarare.space> writes:
>
> > 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.
>
> Looks good to me, please push, thanks!
Thank you! I have applied v2 as c8529c32010a...a900fa3c6c81.
prev parent reply other threads:[~2024-03-09 3:22 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 ` [bug#69429] [PATCH v2 0/3] Update Chiron fonts and split outputs Hilton Chain via Guix-patches via
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 ` Hilton Chain via Guix-patches via [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
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=8734t0t7ng.wl-hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=69429-done@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).