From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] gefs: call for testing
Date: Fri, 15 Dec 2023 15:56:17 -0500 [thread overview]
Message-ID: <266AF6AC832C490524EE43472F4AB653@eigenstate.org> (raw)
In-Reply-To: <2BB32B81DF618AB6D873EF7214B9C257@eigenstate.org>
First off -- all, thanks for testing out the FS, and all the
feedback/bug reports I've gotten.
I've just pushed a revision of the on disk format; the last
rev was fine, but I figued I had a chance now to sand out a
few rough spots before too many people started using this.
I hope (but don't promise yet) that future updates should be
compatible.
Second, I'm aware of old snapshots sometimes getting fucked;
finding and fixing that is my next thing. Hope to have some
updates on that front soon.
Quoth ori@eigenstate.org:
> In the last few weeks, GEFS has moved from "will definitely eat
> your data" to "will likely eat your data". So, it's about time
> to get more people trying it out.
>
> be0ba has written a script to set up a gefs root, so it's easy
> to create a test install with a gefs root:
>
> https://tcp80.org/grobe0ba/gefsroot/HEAD/info.html
>
> For everyone that's already been testing and sending me reports,
> thanks!
>
next prev parent reply other threads:[~2023-12-15 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 16:22 ori
2023-12-15 20:56 ` ori [this message]
2023-12-16 19:25 ` ori
2023-12-18 23:51 ` ori
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=266AF6AC832C490524EE43472F4AB653@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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 NNTP newsgroup(s).