From: Jan Kara <jack@suse.cz>
To: Carlos Maiolino <cmaiolino@redhat.com>
Cc: Jan Kara <jack@suse.cz>, Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org
Subject: Re: Ext4 developers get-together at the Collab Summit
Date: Fri, 18 Jan 2013 18:14:57 +0100 [thread overview]
Message-ID: <20130118171457.GA18458@quack.suse.cz> (raw)
In-Reply-To: <20130118155345.GA22451@localhost.localdomain>
Hi,
On Fri 18-01-13 10:53:45, Carlos Maiolino wrote:
> On Wed, Jan 16, 2013 at 01:01:56PM +0100, Jan Kara wrote:
> > Hello Ted,
> >
> > On Mon 14-01-13 09:48:00, Ted Tso wrote:
> > > The Linux Foundation's Collaboration Summit is April 15-17th,
> > > and the Linux Storage, File System, and MM Summit is April 18-19th in
> > > San Francisco (at the Parc 55 hotel).
> > >
> > > I'd like to organize an ext4 developer's meeting during the
> > > Collab Summit sometime April 15-17th, since so many of us will hopefully
> > > be attending LSF. (The CFP will hopefully be coming soon for LSF.)
> > >
> > > If you're interested in attending, please reply to this thread,
> > > and include some suggested topics that you'd be interested in
> > > discussing. Based on the number of topics and the number of people who
> > > are planning on attending, I'll know how much time we need to reserve
> > > and how big of a room to request.
> > I'd be interested in attending the ext4 meeting this year. What I'd like
> > to do for the meeting is creating a "map" of ext4 mount options / features
> > where we'd see what mount options do we have, which options (or fs features)
> > work together and which don't. Then we can either convince ourselves the
> > situation with too many / too complex interactions isn't that bad or we can
> > come up with simplifications to work on.
>
> I think that would be useful to extend this discussion to ext2/ext3 mount
> options inclusive and merge my suggested topic with this one to find a better
> approach of how to deal with all possible mount options existing in ext4 module
> for all extX filesystem family.
I don't know but I don't have problems with the number of ext2/ext3
options and their combination work as expected. Furthermore even if we
found some possible simplifications, ext2 and ext3 are in
maintenance-mostly mode so some larger changes to features are really out
of question anyway. So I don't think it would be worth the time. But if you
have some particular ext2/3 mount options you have problem with, I'm happy
to listen.
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2013-01-18 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 14:48 Ext4 developers get-together at the Collab Summit Theodore Ts'o
2013-01-16 12:01 ` Jan Kara
2013-01-16 16:15 ` Eric Sandeen
2013-01-18 15:39 ` Ric Wheeler
2013-01-18 15:53 ` Carlos Maiolino
2013-01-18 17:14 ` Jan Kara [this message]
2013-01-17 13:15 ` Zheng Liu
2013-01-18 8:06 ` Tao Ma
2013-01-18 1:45 ` Zhi Yong Wu
2013-01-18 1:57 ` Zhi Yong Wu
2013-01-18 12:06 ` Carlos Maiolino
2013-01-18 17:27 ` Jan Kara
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=20130118171457.GA18458@quack.suse.cz \
--to=jack@suse.cz \
--cc=cmaiolino@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 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).