From: pukkamustard <pukkamustard@posteo.net>
To: Christopher Lemmer Webber <cwebber@dustycloud.org>
Cc: guile-user@gnu.org
Subject: Re: Encoding for Robust Immutable Storage (ERIS) and Guile
Date: Thu, 10 Dec 2020 10:02:38 +0100 [thread overview]
Message-ID: <86tusu5901.fsf@posteo.net> (raw)
In-Reply-To: <87lfe621h4.fsf@dustycloud.org>
> Congratulations pukkamustard, I really am excited by and respect
> the
> work you're doing on this. I think it's probably the proper
> replacement
> slot for the storage work I'm doing in Spritely.
Thank you!
> Once Spritely Goblins gets ported to Guile it'll be really fun
> to
> combine these two things. :)
I agree! Looking forward to hacking on Spirtely in Guile...
-pukkamustard
prev parent reply other threads:[~2020-12-10 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 12:50 Encoding for Robust Immutable Storage (ERIS) and Guile pukkamustard
2020-12-09 16:50 ` Ludovic Courtès
2020-12-10 8:27 ` pukkamustard
2020-12-11 8:10 ` Ludovic Courtès
2020-12-09 20:01 ` Christopher Lemmer Webber
2020-12-10 9:02 ` pukkamustard [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=86tusu5901.fsf@posteo.net \
--to=pukkamustard@posteo.net \
--cc=cwebber@dustycloud.org \
--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).