linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Josh Boyer <jwboyer@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	jffs-dev@axis.com, David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH/RFC] Delete JFFS (version 1)
Date: Tue, 12 Dec 2006 08:02:35 -0500	[thread overview]
Message-ID: <457EA86B.5010407@garzik.org> (raw)
In-Reply-To: <625fc13d0612120456p1d74663fp21e40ee84a8819bc@mail.gmail.com>

Josh Boyer wrote:
> On 12/12/06, Jeff Garzik <jeff@garzik.org> wrote:
>> I have created the 'kill-jffs' branch of
>> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git that
>> removes fs/jffs.
>>
>> I argue that you can count the users (who aren't on 2.4) on one hand,
>> and developers don't seem to have cared for it in ages.
>>
>> People are already talking about jffs2 replacements, so I propose we zap
>> jffs in 2.6.21.
> 
> I'm usually all for killing broken code, but JFFS isn't really broken
> is it?  Is there some burden it's causing by being in the kernel at
> the moment?

It's always been the case that we remove Linux kernel code when the 
number of users (and more importantly, developers) drops to near-nil.

Every line of code is one more place you have to audit when code 
changes, one more place to update each time the VFS API is touched.

When it's more likely to get struck by lightning than encounter 
filesystem X on a random hard drive in the field, filesystem X need not 
be in the kernel.

IMO, of course :)

	Jeff




  reply	other threads:[~2006-12-12 13:02 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-12 12:39 [PATCH/RFC] Delete JFFS (version 1) Jeff Garzik
2006-12-12 12:56 ` Josh Boyer
2006-12-12 13:02   ` Jeff Garzik [this message]
2006-12-12 13:06     ` Josh Boyer
2006-12-12 13:07       ` David Woodhouse
2006-12-12 13:09     ` Jeff Garzik
2006-12-12 17:01     ` Bill Nottingham
2006-12-12 17:20       ` Jeff Garzik
2006-12-12 17:28       ` Alan
2006-12-19 10:56         ` David Weinehall
2006-12-12 12:58 ` Jörn Engel
2006-12-12 17:53 ` Andrew Morton
2006-12-12 18:38   ` Josh Boyer
2006-12-12 21:49     ` Andreas Dilger
2006-12-13  7:06       ` Jörn Engel
2007-03-09 23:13 ` Stefan Monnier

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=457EA86B.5010407@garzik.org \
    --to=jeff@garzik.org \
    --cc=akpm@osdl.org \
    --cc=dwmw2@infradead.org \
    --cc=jffs-dev@axis.com \
    --cc=jwboyer@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).