From: Jeff Mahoney <jeffm@suse.com>
To: reiserfs-devel <reiserfs-devel@vger.kernel.org>
Subject: [ANNOUNCE] reiserfsprogs 3.6.24
Date: Mon, 26 Aug 2013 17:01:55 -0400 [thread overview]
Message-ID: <521BC243.2040101@suse.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
Hi all -
I'm happy to announce the release of reiserfsprogs 3.6.24.
This is a minor maintenance release and contains the following changes
since 2.6.23:
- reiserfeprogs: autogenerate the version number in the man pages
- journal: fix division by 0 with one transaction in log (crash)
- CREDITS/CONTACT: remove non-historical references to namesys.com
- resize_reiserfs: fix > 8TB printf formatting
- man: create links to common-prefix command names
- reiserfsprogs: add symlinks for debugreiserfs and reiserfstune
It is available via the kernel.org ftp site at:
http://ftp.kernel.org/pub/linux/kernel/people/jeffm/reiserfsprogs/v3.6.24/
The next release will be larger and include major cleanups as well as
the export of a shared library for other programs to use. I intend on
pushing most of those changes fairly quickly.
-Jeff
--
Jeff Mahoney
SUSE Labs
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
reply other threads:[~2013-08-26 21:01 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=521BC243.2040101@suse.com \
--to=jeffm@suse.com \
--cc=reiserfs-devel@vger.kernel.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).