From: "Joshua \"Youlysses\" S. Grant" <youlysses@riseup.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile-2D 0.1 released
Date: Fri, 27 Sep 2013 19:55:57 -0500 [thread overview]
Message-ID: <1380329757.864.6.camel@battlestallion> (raw)
In-Reply-To: <CAJ=RwfbK4hRj4WGgfOZ2jGvZimLrh-RHdW2ZEFU_=1P6hm9LpA@mail.gmail.com>
Congrats! I'm more-or-less "hard at work" packaging related components,
needed to get it going via Guix! I just finished packaging FTGL, I'm
working on SDL right now and will hopefully get guile-sdl going
thereafter, and I'm just waiting for Guile-Figl -- but have no idea if
0.1 will be released before the hackathon is over. Either way, it's not
all-too far off.
In-general though, very cool and fun looking tech and in the coming
months, I'm really excited to play around with it.
Best regards,
Joshua "Youlysses" S. Grant
prev parent reply other threads:[~2013-09-28 0:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-27 23:11 Guile-2D 0.1 released Thompson, David
2013-09-28 0:55 ` Joshua "Youlysses" S. Grant [this message]
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=1380329757.864.6.camel@battlestallion \
--to=youlysses@riseup.net \
--cc=dthompson2@worcester.edu \
--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).