[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20071024175549.GA13406@atrey.karlin.mff.cuni.cz>
Date: Wed, 24 Oct 2007 19:55:49 +0200
From: Jan Kara <jack@...e.cz>
To: Avantika Mathur <mathur@...ux.vnet.ibm.com>
Cc: linux-ext4 <linux-ext4@...r.kernel.org>
Subject: Re: Ext4 devel interlock meeting minutes (October 22, 2007)
Hello,
Sorry for not taking part in the call but I was just on my way from NY
to Prague...
> Ext4 Developer Interlock Call
> October 22, 2007: Meeting Minutes
>
> Attendees: Mingming Cao, Andreas Dilger, Eric Sandeen, Dave Kleikamp,
> Jose Santos, Aneesh Veetil, Valerie Clement, Avantika Mathur
>
> - There has been discussion on linux-ext4 about overflow in ext2 with 64
> KB block size. Discussed adding an incompat flag to this feature and
> concluded that it is too late to do this; it will be treated as a bug fix.
Hmm, why adding an incompat flag? Obviously there's no harm in doing
that but the large block size itself should be enough to protect old
kernels/utils touching it, shouldn't it?
> E2fsprogs
> - Ted has added new branches the the e2fsprogs git tree
> - master: current stable version
> - next: patches expected to go into the next stable version
> - pu: proposed update; patches that are in preliminary review and
> test phase
> - E2fsprogs patches should probably be submitted against the 'next'
> branch of the git tree.
BTW: We still don't have appropriate patches for large block size in
e2fsprogs. I guess I should ping Ted about merging the patch once more.
Honza
--
Jan Kara <jack@...e.cz>
SuSE CR Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists