From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Guile Book
Date: Sat, 26 Mar 2011 22:34:09 +0100 [thread overview]
Message-ID: <m3bp0xefce.fsf@unquote.localdomain> (raw)
In-Reply-To: <8739mbc5aj.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 25 Mar 2011 21:29:40 +0100")
On Fri 25 Mar 2011 21:29, ludo@gnu.org (Ludovic Courtès) writes:
> Mike Gran <spk121@yahoo.com> writes:
>
>> The Guile web site links to a doc on lonelycactus.com, which I'm going
>> to repurpose at somepoint in the future. The doc is way obsolete, so it
>> should probably be de-linked.
>
> Done,
At a user's request I tarred up a copy for posterity, at
http://www.gnu.org/software/guile/archive/lonelycactus-guilebook.tar.gz.
Let me know if that's not OK.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-03-26 21:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 22:14 Guile Book Mike Gran
2011-03-23 2:28 ` nalaginrut
2011-03-25 20:29 ` Ludovic Courtès
2011-03-26 21:34 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-23 14:13 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=m3bp0xefce.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).