From: Dmitry Polyakov <liltechdude@gmail.com>
To: guile-user@gnu.org
Subject: fibers doc: fix typo
Date: Sat, 15 Oct 2022 16:51:02 +0500 [thread overview]
Message-ID: <878rlhjoex.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 223 bytes --]
Fiber's README tells me to send this path here, IIUC:
--8<---------------cut here---------------start------------->8---
Mailing List: `guile-user@gnu.org`
--8<---------------cut here---------------end--------------->8---
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-doc-fix-typo.patch --]
[-- Type: text/x-patch, Size: 1007 bytes --]
From 0a2639457a6308e641e09eb00aaa7dcb4eed5dba Mon Sep 17 00:00:00 2001
From: Dmitry Polyakov <liltechdude@gmail.com>
Date: Sat, 15 Oct 2022 16:42:05 +0500
Subject: [PATCH] doc: fix typo
* fibers.texi (Concurrent Web Server): fix typo
---
fibers.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/fibers.texi b/fibers.texi
index 6c82fb9..5f48af0 100644
--- a/fibers.texi
+++ b/fibers.texi
@@ -1383,9 +1383,9 @@ be able to not only the input and output running concurrently, but
also handlers too.
For this reason, Fibers includes a simple standalone web server that
-uses Guile's Guile's HTTP facilities, but not its web server
-framework. To run a standalone web server, use the @code{(fibers web
-server)} module:
+uses Guile's HTTP facilities, but not its web server framework. To
+run a standalone web server, use the @code{(fibers web server)}
+module:
@example
(use-modules (fibers web server))
base-commit: 19dbc8d3e3864a5612ea5b291280ebf7b42ea644
--
2.38.0
next reply other threads:[~2022-10-15 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 11:51 Dmitry Polyakov [this message]
2022-10-15 14:26 ` fibers doc: fix typo Dmitry Polyakov
2022-10-16 8:42 ` Maxime Devos
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=878rlhjoex.fsf@gmail.com \
--to=liltechdude@gmail.com \
--cc=guile-user@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).