From: David Brownell <david-b@pacbell.net>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
jffs-dev@axis.com
Subject: Re: jffs2 build fixes
Date: Tue, 16 May 2006 08:25:52 -0700 [thread overview]
Message-ID: <200605160825.54972.david-b@pacbell.net> (raw)
In-Reply-To: <20060516150928.GC11656@wohnheim.fh-wedel.de>
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.
next prev parent reply other threads:[~2006-05-16 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200604010831.57875.david-b@pacbell.net>
[not found] ` <200605160755.38606.david-b@pacbell.net>
2006-05-16 15:09 ` jffs2 build fixes Jörn Engel
2006-05-16 15:25 ` David Brownell [this message]
2006-05-16 15:33 ` Jörn Engel
2006-05-16 15:34 ` David Woodhouse
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=200605160825.54972.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=dwmw2@infradead.org \
--cc=jffs-dev@axis.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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