From: Arne Babenhauserheide <arne_bab@web.de>
To: alex.sassmannshausen@gmail.com
Cc: guile-user@gnu.org
Subject: Re: [ANN] Guile Hall Release (v0.2)
Date: Fri, 15 Feb 2019 22:29:41 +0100 [thread overview]
Message-ID: <87sgwon3ju.fsf@web.de> (raw)
In-Reply-To: <87d0ntxbyd.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 264 bytes --]
Alex Sassmannshausen <alex.sassmannshausen@gmail.com> writes:
> This project is part of my overall goal of creating user-friendly basic
> tooling & libraries for Guile to encourage newbies to start building
> with Guile.
Very cool! Thank you!
Best wishes,
Arne
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1076 bytes --]
next prev parent reply other threads:[~2019-02-15 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 16:18 [ANN] Guile Hall Release (v0.2) Alex Sassmannshausen
2019-02-15 21:29 ` Arne Babenhauserheide [this message]
2019-02-16 12:36 ` Neil Jerram
2019-02-16 13:04 ` Alex Sassmannshausen
2019-02-16 13:10 ` Nala Ginrut
2019-02-17 15:32 ` Mike Gran
2019-02-17 16:40 ` Alex Sassmannshausen
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=87sgwon3ju.fsf@web.de \
--to=arne_bab@web.de \
--cc=alex.sassmannshausen@gmail.com \
--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).