From: "Ludovic Courtès" <ludo@gnu.org>
To: Fulbert <fulbert@bluewin.ch>
Cc: 57776-done@debbugs.gnu.org
Subject: bug#57776: [PATCH] * doc/ref/compiler.texi (CPS Soup) : fix small typo in doc (closing paren out of @code{} tag).
Date: Sat, 01 Oct 2022 15:50:24 +0200 [thread overview]
Message-ID: <87a66ffyan.fsf@gnu.org> (raw)
In-Reply-To: <YyCvuFDPtHgT+hza@bluewin.ch> (fulbert@bluewin.ch's message of "Tue, 13 Sep 2022 18:28:40 +0200")
Applied, thanks!
prev parent reply other threads:[~2022-10-01 13:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 16:28 bug#57776: [PATCH] * doc/ref/compiler.texi (CPS Soup) : fix small typo in doc (closing paren out of @code{} tag) Fulbert
2022-10-01 13:50 ` 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=87a66ffyan.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=57776-done@debbugs.gnu.org \
--cc=fulbert@bluewin.ch \
/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).