From: Steve Best <sfbest@us.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] Journaled File System (JFS) release 1.0.19
Date: Fri, 07 Jun 2002 15:49:40 -0500 [thread overview]
Message-ID: <3D011C64.45AC84E5@us.ibm.com> (raw)
Release 1.0.19 of JFS was made available today.
Drop 57 on June 7, 2002 (jfs-2.4-1.0.19.tar.gz
and jfsutils-1.0.19.tar.gz) includes fixes to the file
system and utilities.
Utilities changes
- Fix jfsutils packaging/build error from 1.0.18
File System changes
- Fix powerpc64 compiler warnings
- Fix structure alignment
xdlistlock_t must be the same size as maplock_t, whether pointers are
32 bits or 64 bits.
fix for bugzilla #583, assert(blkno + nblocks <= bmp->db_mapsize) jfs_dmap.
c:464!
- Add Christoph's copyright to files he has significantly contributed to.
- sanitize->clear_inode, remove ->put_inode (Christoph Hellwig)
Rename the JFS->clear_inode from diClearExtension to the more descriptive
jfs_clear_inode, move it ti inode.c and clean it up a bit.
Remove jfs_put_inode as in 2.5
For more details about JFS, please see the patch instructions or changelog.
jfs files.
Steve Best
Linux Technology Center
JFS for Linux http://oss.software.ibm.com/jfs
reply other threads:[~2002-06-07 20:50 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=3D011C64.45AC84E5@us.ibm.com \
--to=sfbest@us.ibm.com \
--cc=linux-kernel@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