From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org
Subject: NILFS 2.0.0-testing-5 release
Date: Mon, 15 Oct 2007 16:19:26 +0900 [thread overview]
Message-ID: <1192432766.3943.35.camel@localhost.localdomain> (raw)
Dear NILFS users,
We have released NILFS 2.0.0-testing-5:
A serious bug that caused a deadlock or corruption of
an important internal meta-data file, was fixed.
This fix improve the stability of NILFS volumes
once unmounted and remounted.
The updated package can be found at:
http://www.nilfs.org/en/download.html
Thanks,
Ryusuke Konishi
NILFS team NTT
http://www.nilfs.org/
reply other threads:[~2007-10-15 7:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1192432766.3943.35.camel@localhost.localdomain \
--to=ryusuke-sg5x7nla6pw@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