From: nalaginrut <nalaginrut@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Guile Book
Date: Wed, 23 Mar 2011 10:28:30 +0800 [thread overview]
Message-ID: <1300847310.2583.21.camel@Renee-desktop> (raw)
In-Reply-To: <809751.48139.qm@web37903.mail.mud.yahoo.com>
> Hi-
>
> 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.
>
> The link is on http://www.gnu.org/software/guile/docs/docs.html
> and it points to http://lonelycactus.com/guilebook/
>
> Thanks,
>
> Mike
>
good job! Is this book finished? If so, I'd like to translate it into
Chinese and put it in my wiki. :-)
--
GNU Powered it
GPL Protected it
GOD Blessed it
HFG - NalaGinrut
next prev parent reply other threads:[~2011-03-23 2:28 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 [this message]
2011-03-25 20:29 ` Ludovic Courtès
2011-03-26 21:34 ` Andy Wingo
-- 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=1300847310.2583.21.camel@Renee-desktop \
--to=nalaginrut@gmail.com \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.com \
/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).