From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp106.sbc.mail.mud.yahoo.com ([68.142.198.205]) by canuck.infradead.org with smtp (Exim 4.62 #1 (Red Hat Linux)) id 1Fg1Qs-00087F-NW for linux-mtd@lists.infradead.org; Tue, 16 May 2006 11:26:07 -0400 From: David Brownell To: =?iso-8859-1?q?J=F6rn_Engel?= Date: Tue, 16 May 2006 08:25:52 -0700 References: <200604010831.57875.david-b@pacbell.net> <200605160755.38606.david-b@pacbell.net> <20060516150928.GC11656@wohnheim.fh-wedel.de> In-Reply-To: <20060516150928.GC11656@wohnheim.fh-wedel.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200605160825.54972.david-b@pacbell.net> Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org, Linux Kernel list , jffs-dev@axis.com Subject: Re: jffs2 build fixes List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tuesday 16 May 2006 8:09 am, Jörn Engel wrote: > jffs-dev@axis.com is practically dead. Iirc, the list was used for > the old jffs[1] code. Jffs2 is usually discussed on > linux-mtd@lists.infradead.org (added to Cc:). Then it's overdue for the MAINTAINERS file to be updated ... it seems wrong that the official "where to go" listing for JFFS2 points at a black hole.