From: Andrew Morton <akpm@osdl.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Mingming Cao <cmm@us.ibm.com>,
linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/5] Forking ext4 filesystem from ext3 filesystem
Date: Thu, 10 Aug 2006 13:33:38 -0700 [thread overview]
Message-ID: <20060810133338.8d1f6061.akpm@osdl.org> (raw)
In-Reply-To: <44DB9582.6010609@garzik.org>
On Thu, 10 Aug 2006 16:22:26 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> I strongly disagree that ext3 should be subject to a spring cleaning.
> Comments, whitespace, very very minor things, sure. Trying to get rid
> of brelse() when _many_ other filesystems also use it? ext4 material.
We should seek to minimise the difficulty of cross-porting bugfixes and
enhancements. Putting cleanups in only ext4 works against that.
ext3 will be around for many years yet. We cannot just let it rot due to
some false belief that performing routine maintenance against it will for
some magical reason cause it to break.
next prev parent reply other threads:[~2006-08-10 20:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1155172622.3161.73.camel@localhost.localdomain>
2006-08-10 6:39 ` Andrew Morton
2006-08-10 16:41 ` Mingming Cao
2006-08-10 16:48 ` Jörn Engel
2006-08-10 18:18 ` Andrew Morton
2006-08-10 20:22 ` Jeff Garzik
2006-08-10 20:33 ` Andrew Morton [this message]
2006-08-10 20:52 ` Jeff Garzik
2006-08-10 17:44 ` [Ext2-devel] " Theodore Tso
2006-08-10 18:51 ` Badari Pulavarty
2006-08-10 19:23 ` Andrew Morton
2006-08-10 19:36 ` [Ext2-devel] " Dave Kleikamp
2006-08-10 19:54 ` Andrew Morton
2006-08-10 20:12 ` Jeff Garzik
2006-08-10 20:13 ` Jeff Garzik
2006-08-10 20:27 ` Andrew Morton
2006-08-10 21:00 ` Jeff Garzik
2006-08-10 21:11 ` [Ext2-devel] " Alex Tomas
2006-08-10 22:18 ` Andrew Morton
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=20060810133338.8d1f6061.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cmm@us.ibm.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=jeff@garzik.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®