From: Thien-Thi Nguyen <ttn@gnuvola.org>
To: guile-user@gnu.org
Subject: Re: Updating GNU Serveez for Guile 2.0
Date: Tue, 25 Jan 2011 22:40:02 +0100 [thread overview]
Message-ID: <87lj28hdcd.fsf@ambire.localdomain> (raw)
In-Reply-To: <87bp361gi0.fsf@gnu.org> ("Ludovic Courtès"'s message of "Mon, 24 Jan 2011 16:13:59 +0100")
() ludo@gnu.org (Ludovic Courtès)
() Mon, 24 Jan 2011 16:13:59 +0100
I was just referring to the asynchronous ‘getaddrinfo’ stuff,
not to all of Serveez.
Ah, why didn't you say so in the first place? No objections there.
next prev parent reply other threads:[~2011-01-25 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 5:35 Updating GNU Serveez for Guile 2.0 Mike Gran
2011-01-23 21:46 ` Ludovic Courtès
2011-01-24 7:19 ` Thien-Thi Nguyen
2011-01-24 15:13 ` Ludovic Courtès
2011-01-25 21:40 ` Thien-Thi Nguyen [this message]
2011-01-26 17:02 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2011-01-24 14:28 Mike Gran
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=87lj28hdcd.fsf@ambire.localdomain \
--to=ttn@gnuvola.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).