From: Zhu Zihao <all_but_last@163.com>
To: 57013@debbugs.gnu.org
Subject: [bug#57013] Acknowledgement ([PATCH] Fix mu4e in mu 1.8.7.)
Date: Sat, 06 Aug 2022 11:11:47 +0800 [thread overview]
Message-ID: <86h72q2hf1.fsf@163.com> (raw)
In-Reply-To: <CA+rDc=CY0yoM2CJvEqOqcKApr3ix-MgPWezLzNy+e-PCSgqnPQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 178 bytes --]
For maintainers: Please also cc to this mail address for discussion. :)
--
Retrieve my PGP public key:
gpg --recv-keys 481F5EEEBA425ADC13247C76A6E672D981B8E744
Zihao
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 255 bytes --]
next prev parent reply other threads:[~2022-08-06 3:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 2:36 [bug#57013] [PATCH] Fix mu4e in mu 1.8.7 Zhu Zihao
2022-08-06 3:11 ` Zhu Zihao [this message]
2022-08-19 5:35 ` [bug#57013] Acknowledgement ([PATCH] Fix mu4e in mu 1.8.7.) Zhu Zihao
2022-08-19 17:59 ` bug#57013: [PATCH] Fix mu4e in mu 1.8.7 Tobias Geerinckx-Rice 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=86h72q2hf1.fsf@163.com \
--to=all_but_last@163.com \
--cc=57013@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).