From: Skyler Ferris via Guix-patches via <guix-patches@gnu.org>
To: 67786@debbugs.gnu.org
Subject: [bug#67786] doc: Add documentation for define-record-type*
Date: Fri, 29 Dec 2023 00:12:01 +0000 [thread overview]
Message-ID: <afc9e985-f66b-426e-b344-bfc3c9544622@protonmail.com> (raw)
In-Reply-To: <b843a199-ad7c-43e4-8fe3-4f7bd77989b3@protonmail.com>
Hello again,
I'm not sure if the problem is on my end. I reviewed the logs for the
initial message I sent on December 11 and for the one I tried to send
yesterday. In both cases, exim indicates that it connected to the
appropriate endpoint, wrote a chunked message (BDAT), concluded with a
line like "SMTP<< 250 2.0.0 Ok: <number> bytes queued as <id>", then
closed the connection. The only difference is that when sending to
guix-patches@gnu.org exim ended up talking to eggs.gnu.org, but when
sending to this bug's email address it talked to debbugs.gnu.org. Is
there someone I can talk to in order to help diagnose this issue?
Thanks,
Skyler
next prev parent reply other threads:[~2023-12-29 0:13 UTC|newest]
Thread overview: 8+ 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 ` [bug#67787] Acknowledgement ([PATCH] doc: Add documentation for define-record-type*) Skyler Ferris via Guix-patches via
2023-12-28 0:29 ` [bug#67786] doc: Add documentation for define-record-type* 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 [this message]
2023-12-29 0:17 ` Skyler Ferris via Guix-patches via
-- strict thread matches above, loose matches on Subject: below --
2024-01-13 19:00 [bug#67788] " skyvine--- via Guix-patches via
2024-01-13 18:57 ` [bug#67786] " 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
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=afc9e985-f66b-426e-b344-bfc3c9544622@protonmail.com \
--to=guix-patches@gnu.org \
--cc=67786@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 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).