From: Chris Mason <mason@suse.com>
To: linux-kernel@vger.kernel.org, reiserfs-list@namesys.com, akpm@osdl.org
Subject: [PATCH] reiserfs v3 patches for 2.6.6-rc2
Date: Fri, 23 Apr 2004 15:54:06 -0400 [thread overview]
Message-ID: <1082750045.12989.199.camel@watt.suse.com> (raw)
Hello all,
Thanks to Andrew for helping to test and feed many of the reiserfs
patches into mainline. I've rediffed against the current -mm and linus
trees:
ftp.suse.com/pub/people/mason/patches/reiserfs/2.6.6-rc2
The directory includes a series file to tell you the order to apply the
patches. The same series file should work with -mm kernels as well
right now.
New in this patch set is data=journal support, which fills out the
compatibility list with the 2.4.x reiserfs data logging patches. Other
patches include:
xattrs and acls (Jeff Mahoney)
warning/error messages that include device names (Jeff Mahoney)
quotas
block allocator improvements
metadata readahead for some types of tree searches
data=journal is experimental, but most of the code changes don't kick in
unless you mount with data=journal.
The rest of the patches should be stable.
-chris
next reply other threads:[~2004-04-23 19:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 19:54 Chris Mason [this message]
2004-04-26 16:59 ` I oppose Chris and Jeff's patch to add an unnecessary additional namespace to ReiserFS Hans Reiser
2004-04-26 17:31 ` Chris Mason
2004-04-26 18:15 ` Hans Reiser
2004-04-26 19:12 ` Mark Hahn
2004-04-26 19:13 ` Chris Mason
2004-04-26 20:40 ` Matthias Andree
2004-04-26 22:20 ` Chris Wright
2004-04-26 23:20 ` Andrew Morton
2004-04-27 17:35 ` Hans Reiser
2004-04-27 18:00 ` Markus Törnqvist
2004-04-26 19:33 ` Christoph Hellwig
2004-04-27 17:29 ` Hans Reiser
2004-04-27 17:34 ` Christoph Hellwig
2004-04-27 17:58 ` Hans Reiser
2004-04-27 18:04 ` Christoph Hellwig
2004-04-28 0:10 ` Stefan Traby
2004-04-27 18:07 ` Jeff Garzik
2004-04-28 5:51 ` Meelis Roos
2004-04-30 16:14 ` David Masover
2004-05-02 4:14 ` Rob Landley
2004-04-26 19:56 ` Matt H.
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=1082750045.12989.199.camel@watt.suse.com \
--to=mason@suse.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
/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