From: Girish Shilamkar <girish@clusterfs.com>
To: Ext4 Mailing List <linux-ext4@vger.kernel.org>
Cc: Andreas Dilger <adilger@clusterfs.com>, Theodore Tso <tytso@mit.edu>
Subject: [Patch 0/13] Patches for e2fsprogs
Date: Tue, 24 Jul 2007 16:34:31 +0530 [thread overview]
Message-ID: <1185275071.3789.65.camel@dhcp4.linsyssoft.com> (raw)
Hi,
I am sending the patches for e2fsprogs as decided in the ext4 conf
call.
The patches are based on e2fsprogs-1.40.1. Some of these patches have
already been sent on the list before.
Patches to follow:
1/13 : iostats.
2/13 : Cleanup.
3/13 : Rpm Check.
4/13 : Allow regular files to be preallocated on-disk.
5/13 : Verify in-inode EA structure.
6/13 : Allow more than 32000 subdirectories [e2fsprogs part]
7/13 : Many inodes in filesystem.
8/13 : Config before command line.
9/13 : Adds two extended options and config file counterparts.
10/13: SLES10 patch which adds -m flag support to fsck
11/13: Uinitialised groups.
12/13: Expand inode size.
13/13: Improve e2fsck heuristics for detecting corrupted inodes.
Thanks,
Girish.
next reply other threads:[~2007-07-24 11:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 11:04 Girish Shilamkar [this message]
2007-07-24 17:25 ` [Patch 0/13] Patches for e2fsprogs Theodore Tso
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=1185275071.3789.65.camel@dhcp4.linsyssoft.com \
--to=girish@clusterfs.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).