From: Raymond Jennings <shentino@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>, Jan Kara <jack@suse.cz>
Cc: 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: Mon, 31 Aug 2015 17:24:28 -0700 [thread overview]
Message-ID: <55E4F03C.1010708@gmail.com> (raw)
In-Reply-To: <55E4D5DE.2030709@gmail.com>
On 08/31/15 15:31, Raymond Jennings wrote:
> On 08/31/15 14:37, Linus Torvalds wrote:
>> On Sun, Aug 30, 2015 at 11:19 PM, Jan Kara <jack@suse.cz> wrote:
>>> The biggest change in the pull is the removal of ext3 filesystem driver
>>> (~28k lines removed).
>> I really am not ready to just remove ext3 without a lot of good
>> arguments. There might well be people who this use ext3 as ext3, and
>> don't want to update. I want more a rationale for removal than "ext4
>> can read old ext3 filesystems".
> I actually would agree that having two drivers for the same filesystem
> is redundant and unneeded code duplication.
>
> That said, I wouldn't mind myself if the ext4 driver were given a very
> grueling regression test to make sure it can actually handle old ext3
> systems as well as the ext3 driver can. Just gutting an entire driver
> because another driver can handle it only makes sense if nothing can
> go wrong and the potential for causing regressions is quite obvious.
>
> I think also that we should remove the ext2 driver before we remove
> the ext3 driver.
>
> My two cents.
Just to ask a general opinion:
Am I right that it's ok for kernel code to be organized how we (the
developers) see fit as long as we don't break userspace or hardware in
the process?
So long as we function properly, should userspace care about how our
source code is structured?
I'm thinking yes, but it might be fruitful to see an answer archived on
the list.
>> Linus
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2015-09-01 0:24 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 [this message]
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
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=55E4F03C.1010708@gmail.com \
--to=shentino@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).