From: Christopher Allan Webber <cwebber@dustycloud.org>
To: Catonano <catonano@gmail.com>
Cc: guile-user@gnu.org, help-guix <help-guix@gnu.org>
Subject: Re: squee
Date: Tue, 18 Apr 2017 14:48:56 -0500 [thread overview]
Message-ID: <87shl5zec7.fsf@dustycloud.org> (raw)
In-Reply-To: <CAJ98PDwvCBWeF5Dxne6nY4zsO5o0sZPuF47A=J9Vb9fwitnJGQ@mail.gmail.com>
Catonano writes:
> Ok, I was just confused, it works like a charm
>
> Sorry for the noise
Ah! No worries about the noise. I'm happy to see someone using squee.
It hasn't gotten much love in the last couple of years. I intend to
return to using it in the not too distant future. If you're interested
in working on improvements to it we should talk. In particular we need
help on code that converts between postgres types and guile native types
more, I think.
David Pirotte also has commit access and can help make decisions on the
project.
next prev parent reply other threads:[~2017-04-18 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-17 9:35 squee Catonano
2017-04-18 12:53 ` squee Catonano
2017-04-18 19:48 ` Christopher Allan Webber [this message]
2017-04-19 2:32 ` squee Catonano
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=87shl5zec7.fsf@dustycloud.org \
--to=cwebber@dustycloud.org \
--cc=catonano@gmail.com \
--cc=guile-user@gnu.org \
--cc=help-guix@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).