From: Jean-Pierre Dion <jean-pierre.dion@bull.net>
To: "Jose R. Santos" <jrs@us.ibm.com>
Cc: linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: Ext4 devel interlock meeting minutes (Sep 10, 2007)
Date: Mon, 17 Sep 2007 15:53:36 +0200 [thread overview]
Message-ID: <46EE86E0.5000206@bull.net> (raw)
In-Reply-To: <20070913103210.62e26236@gara>
Hi Jose,
thank you for these minutes for those who were
not online (me,...) !
To be continued today with Mingming's agenda.
jean-pierre
Jose R. Santos a écrit :
> Attendees: Dave Kleikamp, Andreas Dilger, Jose Santos, Aneesh Kumar,
> Eric Sandeen
>
> - Lack of e2fsprogs support for some of the features is viewed as the
> major roadblocks for declaring ext4 stable. There was talk about
> creating a forked version of the tools to only support ext4 while we
> wait for other features to be implemented in Ted's e2fsprogs tree.
> The goal of this version is to provide users with the means of creating
> and fsck ext4 filesystems in order to increase test coverage. Such
> version would probably not export any libraries and thus not worry
> about ABI breakage issues.
>
> - Most filesystem layout changes are already in the patch queue so
> filesystem format is stable. Other major features are in memory
> changes and thus can be changed/improve/debug after dev status is
> removed.
>
> - Andres express interest in Avantika's automated testing to see if it
> was possible to test different permutation of features to test breakage
> of the ext4 code.
>
> - Jose to post FLEX_BG kernel patch for inclusion into the patch
> queue. Inode and block allocation changes are memory only, so they can
> be added after removal of dev status.
>
> - Lost of talk about the process sending patches to MM before sending
> patches for Linus during the merge window. Eric pointed out that if
> nobody was testing ext4 in mm, then this hole exercise is mostly a
> wasted effort. Andreas and Shaggy pointed out Andrews concerns about
> patches not in mm during the last merge window. Shaggy pointed out
> that Ted's git tree is not always up to date to the latest ext4 patch
> queue and that someone need to regularly maintain a git tree Andrew can
> pull from.
>
> - Even though attendance was low Andreas suggested that a meeting
> notice be sent since a lot of good discussion was made. Everybody
> agree but, nobody took meeting notes and nobody volunteered. :)
>
> Apologies if I left out something important.
>
> -JRS
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
prev parent reply other threads:[~2007-09-17 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 15:32 Ext4 devel interlock meeting minutes (Sep 10, 2007) Jose R. Santos
2007-09-17 13:53 ` Jean-Pierre Dion [this message]
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=46EE86E0.5000206@bull.net \
--to=jean-pierre.dion@bull.net \
--cc=jrs@us.ibm.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).