From: Skyler Ferris via Guix-patches via <guix-patches@gnu.org>
To: 67787@debbugs.gnu.org
Subject: [bug#67787] Acknowledgement ([PATCH] doc: Add documentation for define-record-type*)
Date: Mon, 11 Dec 2023 20:19:24 +0000 [thread overview]
Message-ID: <9a80dc3e-928f-46e6-914b-d483f82421be@protonmail.com> (raw)
In-Reply-To: <handler.67787.B.17023258404363.ack@debbugs.gnu.org>
This is a duplicate of bug 67786. Apologies for the noise.
On 12/11/23 12:18, 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 67787@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.
>
> --
> 67787: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=67787
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
next prev parent reply other threads:[~2023-12-11 20:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 20:16 [bug#67786] [PATCH] doc: Add documentation for define-record-type* Skyler Ferris via Guix-patches via
[not found] ` <handler.67787.B.17023258404363.ack@debbugs.gnu.org>
2023-12-11 20:19 ` Skyler Ferris via Guix-patches via [this message]
2023-12-28 0:29 ` [bug#67786] " Skyler Ferris via Guix-patches via
2023-12-28 1:23 ` Skyler Ferris via Guix-patches via
2023-12-28 2:03 ` Skyler Ferris via Guix-patches via
2023-12-29 0:12 ` Skyler Ferris via Guix-patches via
2023-12-29 0:17 ` Skyler Ferris 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9a80dc3e-928f-46e6-914b-d483f82421be@protonmail.com \
--to=guix-patches@gnu.org \
--cc=67787@debbugs.gnu.org \
--cc=skyvine@protonmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.