From: Eric Sandeen <sandeen@redhat.com>
To: Theodore Tso <tytso@MIT.EDU>
Cc: linux-ext4@vger.kernel.org
Subject: Re: What's cooking in e2fsprogs.git (topics)
Date: Sun, 10 Feb 2008 23:08:11 -0600 [thread overview]
Message-ID: <47AFD83B.7060007@redhat.com> (raw)
In-Reply-To: <20080211045107.GB25089@mit.edu>
Theodore Tso wrote:
> I'ts been a while since I've pushed one of these out. This updates pu
> against the latest "next" branch, so we can make sure all of the
> changes that had been folded into "maint" is included on the pu
> branch. It also includes more work on the tt/extents patches.
> Tune2fs and e2image are now functional with extents, and e2fsck has
> more extents checking added. Still a bit more work to be done there,
> and I also have to add code to deal with symlinks that have the
> EXTENTS_FL flag set.
>
> I've dropped the js/flex-bg branch since it had conflicts with the
> on-disk bg flags, and it had conflicts with the exsting patches that
> caused me concern. Jose, once you regenerate the patch and deal with
> comments, I'll add it back in.
>
> My TODO list:
>
> finish e2fsck extents support
> more flexible mke2fs.conf handling
> EXT4 -- allow mke2fs 8TB without -f
ext3 should be fine as well, right? And I think Josef sent a patch...
-Eric
next prev parent reply other threads:[~2008-02-11 5:08 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 22:42 What's cooking in e2fsprogs.git (topics) Theodore Ts'o, Theodore Ts'o
2007-11-05 2:15 ` Andreas Dilger
2007-11-05 4:32 ` Theodore Tso
2007-11-05 15:06 ` Andreas Dilger
2007-12-17 17:11 ` Theodore Tso
2007-12-17 22:34 ` Andreas Dilger
2007-12-17 22:59 ` Theodore Tso
2007-12-17 23:36 ` Andreas Dilger
2007-12-18 3:32 ` Theodore Tso
2007-12-18 8:13 ` Florian Weimer
2007-12-18 19:10 ` What's cooking in e2fsprogs.git (topics) - [RFC] FLEX_BG bmap and itable allocation patch Jose R. Santos
2008-02-11 4:51 ` What's cooking in e2fsprogs.git (topics) Theodore Tso
2008-02-11 5:08 ` Eric Sandeen [this message]
2008-02-11 7:24 ` Theodore Tso
2008-02-19 5:09 ` Theodore Tso
2008-02-20 18:46 ` Eric Sandeen
2008-02-21 14:05 ` Theodore Tso
2008-02-21 16:40 ` Eric Sandeen
2008-02-22 23:14 ` Andreas Dilger
2008-02-23 0:15 ` Theodore Tso
2008-02-25 4:20 ` Andreas Dilger
2008-02-25 15:13 ` Theodore Tso
2008-02-25 16:01 ` Aneesh Kumar K.V
2008-02-25 17:32 ` Eric Sandeen
2008-02-25 20:23 ` Theodore Tso
2008-02-29 15:43 ` Theodore Tso
2008-02-29 19:59 ` Andreas Dilger
2008-02-29 22:49 ` Theodore Tso
2008-03-02 3:24 ` Jose R. Santos
2008-03-05 16:59 ` Jose R. Santos
2008-03-13 18:11 ` Theodore Tso
2008-03-20 20:32 ` Theodore Tso
2008-04-02 0:09 ` Theodore Tso
2008-04-07 17:12 ` Theodore Tso
2008-04-18 18:43 ` Theodore Tso
2008-04-21 16:41 ` Theodore Tso
2008-04-23 7:32 ` Aneesh Kumar K.V
2008-04-23 11:55 ` Theodore Tso
2008-04-23 18:58 ` Aneesh Kumar K.V
2008-04-28 19:44 ` The changes I made to the undo-mgr (Re: What's cooking in e2fsprogs.git (topics)) Theodore Tso
2008-05-24 23:54 ` What's cooking in e2fsprogs.git (topics) Theodore Tso
2008-06-03 2:40 ` Theodore Tso
2008-06-17 12:03 ` Theodore Tso
2008-03-02 23:50 ` Christian Kujau
-- strict thread matches above, loose matches on Subject: below --
2007-10-16 4:48 Theodore Ts'o
2007-10-16 5:36 ` Aneesh Kumar K.V
2007-10-16 16:41 ` Jose R. Santos
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=47AFD83B.7060007@redhat.com \
--to=sandeen@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.