From: Jan Kara <jack@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
Mel Gorman <mgorman@techsingularity.net>, Jan Kara <jack@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [GIT PULL] Ext3 removal, quota & udf fixes
Date: Tue, 15 Sep 2015 07:31:20 +0200 [thread overview]
Message-ID: <20150915053120.GC2392@quack.suse.cz> (raw)
In-Reply-To: <CA+55aFy4LZP3_eNq=tBjkbPaVVRuQxuXRXV=+yLsvqzD9jXqyA@mail.gmail.com>
On Wed 02-09-15 16:47:24, Linus Torvalds wrote:
> On Wed, Sep 2, 2015 at 11:45 AM, Darrick J. Wong
> <darrick.wong@oracle.com> wrote:
> > On Wed, Sep 02, 2015 at 05:52:01PM +0100, Mel Gorman wrote:
> >> On the flip side, there does not appear to be any good reason for
> >> keeping the ext3 driver around because if there ever is a case where an
> >> old kernel is required to mount an ext3 filesystem then it appears the
> >> ext4 developers would consider it a bug.
> >
> > Yes, that would be a bug.
>
> So the thing I'm happy to see is that the ext4 developers seem to
> unanimously agree that maintaining ext3 compatibility is part of their
> job, and nobody seems to be arguing for keeping ext3 around. As long
> as any possible regressions from ext3 removal have a clear "yup, it's
> on us" from the ext4 people, I don't mind removing it. I was
> expecting ext4 people to not be thrilled about supporting possible
> legacy cases.
>
> As a result, I'm personally convinced. I'll get around to the
> filesystem pulls tomorrow unless something unexpected happens, and
> expect to pull Jan's ext3-removal tree unless somebody suddenly speaks
> up.
Thanks for pulling. Next time I will do a better job when writing a
changelog for such large change. We were discussing this on and off for
last two years with other ext4 developers so when I finally decided the
time for removal has come, it felt obvious to me...
Honza
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2015-09-15 5:31 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 6:19 [GIT PULL] Ext3 removal, quota & udf fixes Jan Kara
2015-08-31 21:37 ` Linus Torvalds
2015-08-31 22:31 ` Raymond Jennings
2015-08-31 22:39 ` Linus Torvalds
2015-08-31 23:03 ` Raymond Jennings
2015-09-01 2:53 ` Theodore Ts'o
2015-09-01 12:52 ` Eric Sandeen
2015-09-01 15:17 ` Jeff Mahoney
2015-09-01 0:24 ` Raymond Jennings
2015-09-01 6:44 ` Christoph Hellwig
2015-09-01 10:29 ` Albino B Neto
2015-09-01 19:39 ` Austin S Hemmelgarn
2015-09-01 23:58 ` Theodore Ts'o
2015-09-02 16:58 ` Austin S Hemmelgarn
2015-09-02 3:30 ` Albino B Neto
2015-09-02 5:46 ` Raymond Jennings
2015-09-02 13:28 ` Austin S Hemmelgarn
2015-09-02 11:58 ` Chuck Ebbert
2015-09-02 13:33 ` Austin S Hemmelgarn
2015-09-01 0:23 ` Andreas Dilger
2015-09-02 16:52 ` Mel Gorman
2015-09-02 18:45 ` Darrick J. Wong
2015-09-02 23:47 ` Linus Torvalds
2015-09-03 11:28 ` Albino B Neto
2015-09-03 21:49 ` Darrick J. Wong
2015-09-15 5:31 ` Jan Kara [this message]
2015-09-03 18:22 ` Richard Yao
2015-09-03 18:36 ` Eric Sandeen
2015-09-03 19:13 ` Richard Yao
2015-09-03 18:36 ` Darrick J. Wong
2015-09-03 19:16 ` Richard Yao
2015-09-03 19:36 ` Darrick J. Wong
2015-09-03 22:26 ` Richard Yao
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=20150915053120.GC2392@quack.suse.cz \
--to=jack@suse.cz \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@techsingularity.net \
--cc=torvalds@linux-foundation.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).