From: divoplade <d@divoplade.fr>
To: tomas@tuxteam.de
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile web server example serving static files
Date: Sun, 20 Sep 2020 09:52:08 +0200 [thread overview]
Message-ID: <241003da760aff49d7e3a56ed6454f723f3a95b6.camel@divoplade.fr> (raw)
In-Reply-To: <20200920074841.GA28825@tuxteam.de>
Le dimanche 20 septembre 2020 à 09:48 +0200, tomas@tuxteam.de a écrit :
> Something to keep in mind when talking to "other cultures" --
> they are our neighbours, after all :-)
I did not recommend using this term. There was a question in the source
code asking why guile used a different terminology; I put the
explanation why, with the relevant citation (because the section is
huge). That's all.
next prev parent reply other threads:[~2020-09-20 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 21:45 Guile web server example serving static files Zelphir Kaltstahl
2020-09-18 5:56 ` divoplade
2020-09-19 10:39 ` Zelphir Kaltstahl
2020-09-20 7:48 ` tomas
2020-09-20 7:52 ` divoplade [this message]
2020-09-20 8:29 ` tomas
2020-09-20 8:54 ` divoplade
2020-09-20 9:07 ` tomas
2020-09-18 7:47 ` Dr. Arne Babenhauserheide
2020-09-19 10:57 ` Zelphir Kaltstahl
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=241003da760aff49d7e3a56ed6454f723f3a95b6.camel@divoplade.fr \
--to=d@divoplade.fr \
--cc=guile-user@gnu.org \
--cc=tomas@tuxteam.de \
/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).