From: 宋文武 <iyzsong@envs.net>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] Guile-OpenGL 0.2.0 released
Date: Sat, 13 May 2023 20:07:58 +0800 [thread overview]
Message-ID: <87ilcwqvs1.fsf@envs.net> (raw)
In-Reply-To: <CAJ=RwfYmEPfzFZa2QpL5ugFmhCkNs291tCirgp-tz0=Gem5Oyg@mail.gmail.com> (David Thompson's message of "Sat, 13 May 2023 07:41:53 -0400")
"Thompson, David" <dthompson2@worcester.edu> writes:
> Hey Guilers,
>
> I have recently become the new maintainer of Guile-OpenGL and I'm
> happy to announce that version 0.2.0 has been released! 0.1.0 was
> released all the way back in 2014(!!) and the build system requires
> multiple hacks to build with Guile 3. This release is primarily to
> fix those issues before the upcoming Lisp Game Jam. [0] Future
> releases will feature more high-level wrappers for low-level GL
> bindings.
Congrats and thank you for the new release!
prev parent reply other threads:[~2023-05-13 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 11:41 [ANN] Guile-OpenGL 0.2.0 released Thompson, David
2023-05-13 12:07 ` 宋文武 [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=87ilcwqvs1.fsf@envs.net \
--to=iyzsong@envs.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).