From: dante <subscriptions@posteo.eu>
To: <9front@9front.org>
Subject: Re: [9front] Cambrian
Date: Sat, 26 Jul 2014 15:49:30 +0200 [thread overview]
Message-ID: <9392616f10737d6f9457921b4d7ae78f@posteo.de> (raw)
In-Reply-To: <CAEAzY3_yObSktZFqBdQP+rTRkoAyhRcZgQ+YRuOzF45ArLGV4Q@mail.gmail.com>
In my modest experience, hjfs keeps running into errors and blocking
the system.
Not so with fossil. Will try cwfs.
On 24.07.2014 11:09, Aram Hăvărneanu wrote:
> I mean the bug where it randomly corrupts itself.
>
> Cwfs is rock solid, I don't know how reliable hjfs is, but many people
> use it.
>
> --
> Aram Hăvărneanu
next prev parent reply other threads:[~2014-07-26 13:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 8:11 Cambrian dante
2014-07-24 8:44 ` [9front] Cambrian Aram Hăvărneanu
2014-07-24 9:03 ` dante
2014-07-24 9:09 ` Aram Hăvărneanu
2014-07-26 13:49 ` dante [this message]
2014-07-26 14:01 ` Kurt H Maier
2014-07-26 18:46 ` sl
2014-07-27 7:42 ` dante
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=9392616f10737d6f9457921b4d7ae78f@posteo.de \
--to=subscriptions@posteo.eu \
--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).