From: Dominic Martinez <dom@dominicm.dev>
To: 54104@debbugs.gnu.org
Subject: [bug#54104] [PATCH] gnu: Add fcitx5-anthy
Date: Wed, 09 Mar 2022 10:47:13 -0500 [thread overview]
Message-ID: <87lexjf7m6.fsf@dominicm.dev> (raw)
In-Reply-To: <20220222001349.24808-2-dom@dominicm.dev>
[-- Attachment #1: Type: text/plain, Size: 163 bytes --]
Just wanted to ping this patch; I've tested this on my personal
fcitx5 setup and it works, so unless there is a formatting issue I
think this is good to merge.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2022-03-09 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 0:13 [bug#54103] dom
2022-02-22 0:13 ` [bug#54104] [PATCH] gnu: Add fcitx5-anthy dom
2022-03-09 15:47 ` Dominic Martinez [this message]
2022-03-10 18:59 ` bug#54104: " Nicolas Goaziou
[not found] ` <handler.54103.B.16455186134307.ack@debbugs.gnu.org>
2022-02-22 14:17 ` bug#54103: Acknowledgement () Dominic Martinez
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=87lexjf7m6.fsf@dominicm.dev \
--to=dom@dominicm.dev \
--cc=54104@debbugs.gnu.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.
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).