unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Catonano <catonano@gmail.com>
To: Alex Sassmannshausen <alex.sassmannshausen@gmail.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] Guile Hall 0.3.0 released
Date: Sat, 16 May 2020 18:22:58 +0200	[thread overview]
Message-ID: <CAJ98PDxfwXzQa6h_BkS6AkLWYTCXz8Ao+s=S8hoQD+q=oDmRzQ@mail.gmail.com> (raw)
In-Reply-To: <87k11bdh0k.fsf@gmail.com>

Il giorno sab 16 mag 2020 alle ore 17:41 Alex Sassmannshausen <
alex.sassmannshausen@gmail.com> ha scritto:

> Hello,
>
> I have the pleasure to announce that I have today released Guile Hall
> 0.3.0.
>
>
Thank you Alex !

I believe the most important step now would be to write a manual at least
partially

So that guile-hall could be mentioned in the Guile manual

I think it'd be an important step in the Guile user experience story


  parent reply	other threads:[~2020-05-16 16:22 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 15:41 [ANN] Guile Hall 0.3.0 released Alex Sassmannshausen
2020-05-16 16:14 ` Jack Hill
2020-05-16 16:22 ` Catonano [this message]
2020-05-16 20:57   ` Alex Sassmannshausen
2020-05-17  5:13     ` Catonano
2020-05-17 15:35       ` Alex Sassmannshausen
2020-05-17 17:37         ` Catonano
2020-05-17 18:31           ` Arne Babenhauserheide
2020-05-17 20:55             ` Alex Sassmannshausen
2020-05-18  5:43               ` Arne Babenhauserheide
2020-05-17 20:48           ` Alex Sassmannshausen
2020-05-18 16:19             ` Catonano
2020-05-20 11:45               ` Catonano
2020-05-20 11:46                 ` Alex Sassmannshausen
2020-05-20 15:58                   ` Catonano
2020-05-21 10:00                     ` Catonano
2020-05-21 10:03                       ` Alex Sassmannshausen
2020-05-22  5:16                         ` Catonano
2020-05-24 21:22                           ` Alex Sassmannshausen
2020-05-25  6:31                             ` Catonano
2020-05-25  7:13                               ` Alex Sassmannshausen
2020-05-25  7:51                                 ` Catonano
2020-05-26 14:37                                   ` Catonano
2020-05-27 20:52                             ` Ludovic Courtès
2020-05-28  5:01                               ` Catonano
2020-05-28 12:32                                 ` Ludovic Courtès
2020-05-28 12:35                                   ` Catonano
2020-05-28 15:54                                     ` Ludovic Courtès
2020-05-28 17:26                                       ` Catonano
2020-05-29  8:27                                         ` Ludovic Courtès
2020-05-29  9:09                                           ` Catonano
2020-05-29 10:52                                             ` Alex Sassmannshausen
2020-05-17 16:36       ` Christopher Lemmer Webber
2020-05-17 20:40         ` Alex Sassmannshausen
2020-05-17 20:21 ` Jérémy Korwin-Zmijowski
2020-05-18 15:43 ` Nala Ginrut

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='CAJ98PDxfwXzQa6h_BkS6AkLWYTCXz8Ao+s=S8hoQD+q=oDmRzQ@mail.gmail.com' \
    --to=catonano@gmail.com \
    --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).