From: dan <igaryhe@gmail.com>
To: 51668@debbugs.gnu.org
Subject: [bug#51668] Acknowledgement ([PATCH] gnu: Add fcitx5-rime.)
Date: Mon, 8 Nov 2021 09:56:54 +0800 [thread overview]
Message-ID: <CAFp0n+71erj_neM+fOcmMrSwFo0dNhKmX9Uv89BYfF6czMY_1g@mail.gmail.com> (raw)
In-Reply-To: <handler.51668.B.163630402220241.ack@debbugs.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
This is a duplication of bug#51667. I submit this mainly because I was
afraid that the previous patch didn't follow the submission guidelines
since I attached 6 patches in the previous submission. If that one is OK,
please ignore this patch.
On Mon, Nov 8, 2021 at 12:54 AM GNU bug Tracking System <
help-debbugs@gnu.org> wrote:
> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
> guix-patches@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 51668@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 51668: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=51668
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
>
[-- Attachment #2: Type: text/html, Size: 1871 bytes --]
next prev parent reply other threads:[~2021-11-08 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-07 15:44 [bug#51668] [PATCH] gnu: Add fcitx5-rime dan
2021-11-08 1:54 ` dan
2021-11-08 8:49 ` bug#51668: " zimoun
[not found] ` <handler.51668.B.163630402220241.ack@debbugs.gnu.org>
2021-11-08 1:56 ` dan [this message]
2021-11-10 17:45 ` [bug#51668] " dan
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=CAFp0n+71erj_neM+fOcmMrSwFo0dNhKmX9Uv89BYfF6czMY_1g@mail.gmail.com \
--to=igaryhe@gmail.com \
--cc=51668@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).