From: Jean Abou Samra <jean@abou-samra.fr>
To: 49686-done@debbugs.gnu.org
Subject: bug#49686: Confusing presence of #f in error message
Date: Wed, 7 Dec 2022 20:58:25 +0100 [thread overview]
Message-ID: <01e32635-469b-5074-d8a9-7914c8a367a9@abou-samra.fr> (raw)
In-Reply-To: <813c9094-b338-bd44-f204-4d5c11084892@abou-samra.fr>
[-- Attachment #1.1: Type: text/plain, Size: 88 bytes --]
This seems to have been fixed, probably in
eb5ecf4944cd646341f7e47dda5396cf96a4b8a3.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
prev parent reply other threads:[~2022-12-07 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 19:12 bug#49686: Confusing presence of #f in error message Jean Abou Samra
2021-08-14 17:41 ` Jean Abou Samra
2022-12-07 19:58 ` Jean Abou Samra [this message]
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=01e32635-469b-5074-d8a9-7914c8a367a9@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=49686-done@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.
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).