From: Eric Sandeen <sandeen@redhat.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Michael Rubin <mrubin@google.com>, Jan Kara <jack@suse.cz>,
lsf-pc@lists.linuxfoundation.org, linux-fsdevel@vger.kernel.org,
linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [LSF/MM TOPIC] Drop ext2/ext3 codebase? When?
Date: Thu, 03 Feb 2011 16:00:47 -0600 [thread overview]
Message-ID: <4D4B258F.6020708@redhat.com> (raw)
In-Reply-To: <AANLkTi=wAX8yLSsbn-zM5t6DrE22asYnz6KdQBfSYuUT@mail.gmail.com>
On 2/3/11 3:57 PM, Amir Goldstein wrote:
> Can you give a rough estimate of how those commits diverge between
> bugfixes, kernel API changes, code cleanups?
Um, maybe by the time LSF rolls around ;) It'd take a while to sift
though.
> Next3 has been following ext3 since 2.6.31 and I remember changes of
> the 2 latter,
> but not many major bugfixes.
>
> I hardly think we can get away with throwing out ext3 code base, but
> maybe it can go
> into bugfixes-only mode? that is unless Jan likes to apply cleanups ;-)
In theory that's what it's been for a couple years already :)
-Eric
> Amir.
>
next prev parent reply other threads:[~2011-02-03 22:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 14:40 [LSF/MM TOPIC] Drop ext2/ext3 codebase? When? Jan Kara
2011-02-03 15:08 ` Eric Sandeen
2011-02-03 19:32 ` Michael Rubin
2011-02-03 19:49 ` Eric Sandeen
2011-02-03 21:57 ` Amir Goldstein
2011-02-03 22:00 ` Eric Sandeen [this message]
2011-02-04 13:59 ` Jan Kara
2011-02-04 0:04 ` Ted Ts'o
2011-02-04 13:17 ` Jan Kara
2011-02-04 17:03 ` Ric Wheeler
2011-02-04 17:17 ` [Lsf-pc] " James Bottomley
2011-02-05 18:43 ` Trond Myklebust
2011-02-07 17:21 ` Mingming Cao
2011-02-12 11:05 ` Amir Goldstein
2011-02-14 17:25 ` Jan Kara
2011-02-14 19:00 ` Amir Goldstein
2011-02-04 13:03 ` Jan Kara
2011-02-04 17:36 ` Andreas Dilger
2011-02-07 16:19 ` Jan Kara
2011-02-07 16:35 ` Andreas Dilger
2011-02-11 11:16 ` Jan Kara
2011-02-11 18:44 ` Michael Rubin
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=4D4B258F.6020708@redhat.com \
--to=sandeen@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linuxfoundation.org \
--cc=mrubin@google.com \
/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).