From: "Ludovic Courtès" <ludo@gnu.org>
To: "Jan \(janneke\) Nieuwenhuizen" <janneke@gnu.org>
Cc: 41716-done@debbugs.gnu.org
Subject: bug#41716: [PATCH] reader: Use invalid rather than illegal.
Date: Wed, 17 Jun 2020 23:27:05 +0200 [thread overview]
Message-ID: <87lfklpemu.fsf@gnu.org> (raw)
In-Reply-To: <20200604192623.10350-1-janneke@gnu.org> (Jan Nieuwenhuizen's message of "Thu, 4 Jun 2020 21:26:23 +0200")
Hey,
"Jan (janneke) Nieuwenhuizen" <janneke@gnu.org> skribis:
> * libguile/read.c (scm_read_string_like_syntax): All characters are
> permitted by law; some aren't valid in certain contexts.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2020-06-17 21:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 19:26 bug#41716: [PATCH] reader: Use invalid rather than illegal Jan (janneke) Nieuwenhuizen
2020-06-17 21:27 ` Ludovic Courtès [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=87lfklpemu.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41716-done@debbugs.gnu.org \
--cc=janneke@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).