From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-sources@gnu.org
Cc: guile-user@gnu.org
Subject: Guile-WWW 2.39 available
Date: Sun, 22 Feb 2015 13:03:01 +0100 [thread overview]
Message-ID: <87ioeuqhl6.fsf@zigzag.favinet> (raw)
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
release notes:
Maintenance release; keeping the flame alive!
I was hoping to have gotten organized enough by now
to put a tip jar up for Guile-WWW, but oh well...
thi
README excerpt:
This is the Guile WWW library, a set of Guile Scheme
modules to facilitate HTTP, URL and CGI programming.
NEWS for 2.39 (2015-02-22):
- doc fix: spell "incompatibility" correctly!
- ‘http:request’ slightly faster
- bootstrap tools upgraded
- GNU Automake 1.15
- Guile-BAUX 20150108.1006.f6573e4
home page:
http://www.nongnu.org/guile-www/
patronage:
http://www.gnuvola.org/patronage.html
--
Thien-Thi Nguyen
GPG key: 4C807502
(if you're human and you know it)
read my lisp: (responsep (questions 'technical)
(not (via 'mailing-list)))
=> nil
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
reply other threads:[~2015-02-22 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87ioeuqhl6.fsf@zigzag.favinet \
--to=ttn@gnuvola.org \
--cc=guile-sources@gnu.org \
--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).