From: "Jörn Engel" <joern@lazybastard.org>
To: Jeff Garzik <jeff@garzik.org>
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 12:58:36 +0000 [thread overview]
Message-ID: <20061212125836.GA13786@lazybastard.org> (raw)
In-Reply-To: <457EA2FE.3050206@garzik.org>
On Tue, 12 December 2006 07:39:26 -0500, Jeff Garzik 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.
You can count them on one finger, I guess. The last time jffs was
proposed for removal, a single person said he still used it and would
like to keep it around. And I haven't seen any patches come forward since.
Jörn
--
Don't patch bad code, rewrite it.
-- Kernigham and Pike, according to Rusty
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-12-12 13:01 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
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 [this message]
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=20061212125836.GA13786@lazybastard.org \
--to=joern@lazybastard.org \
--cc=akpm@osdl.org \
--cc=dwmw2@infradead.org \
--cc=jeff@garzik.org \
--cc=jffs-dev@axis.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).