From: Theodore Ts'o <tytso@mit.edu>
To: "U.Mutlu" <for-gmane@mutluit.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Which newer kernel is OK with ext4?
Date: Fri, 5 Jun 2015 10:30:21 -0400 [thread overview]
Message-ID: <20150605143021.GB26550@thunk.org> (raw)
In-Reply-To: <mkpljk$al6$1@ger.gmane.org>
On Thu, Jun 04, 2015 at 03:59:16PM +0200, U.Mutlu wrote:
> I have many times compiled a kernel and used it successfully,
> but when I dist-upgraded from Debian 7 to Debian 8 it installed
> it's own stock kernel maintained by Debian. No problem to switch
> to a newer kernel from kernel.org, but for me it was unclear
> if and how the ongoing ext4-developments will have an impact on
> existing ext4-partitions. Now I think everything is clear, I'll
> take a newer kernel from kernel.org.
Many Linux kernel developers use at least one or more ext4 file
systems, and they would be very cranky if things became unstable. As
a result, we are regularly running regression tests to make sure we
don't break ext4 users.
This principle holds true for all open source projects, at those with
responsible developers. Emacs is constantly adding features --- would
that lead you to be concerned after upgrading to Debian 8 that you
shouldn't use a new release of emacs because it might corrupt your
source files in the course of using it in normal operations, and send
e-mail to the emacs developer's list asking if it's safe to use "the
new emacs"?
Regards,
- Ted
P.S. There was a typo in my previous message. To be clear, 4.0 is
**NOT** is not a long-term supported kernel. (My previous e-mail
omitted the "not".)
prev parent reply other threads:[~2015-06-05 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 19:50 Which newer kernel is OK with ext4? U.Mutlu
2015-06-04 2:08 ` Theodore Ts'o
2015-06-04 13:59 ` U.Mutlu
2015-06-05 14:30 ` Theodore Ts'o [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=20150605143021.GB26550@thunk.org \
--to=tytso@mit.edu \
--cc=for-gmane@mutluit.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