From: David Arendt <admin-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: Ready for production ?
Date: Wed, 15 Oct 2008 22:44:38 +0200 [thread overview]
Message-ID: <48F65636.5050405@prnet.org> (raw)
Hi,
One thread with exactly this subject was started 12 months ago. So it
would be interested to make the point once again.
I am actually using nilfs2 on a volume where data integrity isn't
important and didn't have any problems until now.
So what would the developers say ? Is it ready for production ?
Congratulations for this very good file system, I really like the idea
behind it.
Bye,
David Arendt
next reply other threads:[~2008-10-15 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 20:44 David Arendt [this message]
[not found] ` <48F65636.5050405-/LHdS3kC8BfYtjvyW6yDsg@public.gmane.org>
2008-10-17 6:09 ` Ready for production ? Ryusuke Konishi
[not found] ` <20081017.150912.86504903.ryusuke-sG5X7nlA6pw@public.gmane.org>
2008-10-17 11:15 ` Daniel Phillips
[not found] ` <200810170415.30644.phillips-sjnr1BIWhQJeoWH0uzbU5w@public.gmane.org>
2008-10-18 2:28 ` Ryusuke Konishi
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=48F65636.5050405@prnet.org \
--to=admin-/lhds3kc8bfytjvyw6ydsg@public.gmane.org \
--cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.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