From: Amirouche <amirouche@hyper.dev>
To: guile-user gnu <guile-user@gnu.org>
Cc: guile-user <guile-user-bounces+amirouche=hyper.dev@gnu.org>
Subject: Re: [ANN] guile-wiredtiger 0.8.1
Date: Fri, 17 May 2019 21:10:58 +0200 [thread overview]
Message-ID: <df12aafb7cec76004963a1c5c2cfff9b@hyper.dev> (raw)
In-Reply-To: <6e997828af6b58786a4ed5c92b2d9d5c@hyper.dev>
On 2019-05-17 12:11, Amirouche wrote:
>>
>> The key word is fine-tuning. That is what makes the database works.
>>
I made a quick fix that was planned but forgot about and made a new
release.
Here is the diff:
https://framagit.org/a-guile-mind/guile-wiredtiger/commit/64f33033e85bcd970d1599c9f54f26dfe462c55e
On a related not, I turned gotofish.scm into a web app running guix
guile-next, and indexing a bunch of scheme related websites. I will
publish the url once the indexing is finished.
Happy week-end!
prev parent reply other threads:[~2019-05-17 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 21:05 [ANN] guile-wiredtiger 0.8.0 Amirouche
2019-05-17 10:11 ` Amirouche
2019-05-17 11:24 ` Nala Ginrut
2019-05-17 12:17 ` Amirouche
2019-05-17 19:10 ` Amirouche [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=df12aafb7cec76004963a1c5c2cfff9b@hyper.dev \
--to=amirouche@hyper.dev \
--cc=guile-user-bounces+amirouche=hyper.dev@gnu.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).