From: Thomas Lord <lord@emf.net>
Subject: Re: Guile 1.8.0 has been released.
Date: Wed, 01 Mar 2006 10:32:47 -0800 [thread overview]
Message-ID: <1141237967.6215.67.camel@localhost.localdomain> (raw)
I know I have only the tiniest sliver of remaining
legitimacy for saying this and I don't mean to claim
any more than the tiniest and most indirect credit but:
I am very proud that you guys have done such good work.
It's a little arrogant to say it but: thank you. Thank
you for adopting and raising "my baby". It looks from
here like Guile is growing up to be a fine, upstanding
piece of software.
-t
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2006-03-01 18:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 18:32 Thomas Lord [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-20 22:03 Guile 1.8.0 has been released Marius Vollmer
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=1141237967.6215.67.camel@localhost.localdomain \
--to=lord@emf.net \
/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).