From: Steve Wahl <steve.wahl@qlogic.com>
To: "Artem B. Bityuckiy" <dedekind@infradead.org>
Cc: linux-mtd@lists.infradead.org, Ian McDonnell <ian@brightstareng.com>
Subject: Re: Suggestion: Give JFFS its own mail list.
Date: Wed, 20 Apr 2005 09:39:58 -0500 [thread overview]
Message-ID: <20050420143958.GI1915@qlogic.com> (raw)
In-Reply-To: <1114006991.32582.11.camel@sauron.oktetlabs.ru>
On Wed, Apr 20, 2005 at 06:23:11PM +0400, Artem B. Bityuckiy wrote:
> On Wed, 2005-04-20 at 09:40 -0400, Ian McDonnell wrote:
> > Is it time to give JFFS/JFFS2 a mail list of its own?
> >
> > I am a user intested in MTD and below but not jffs, and
> > it seams like there's a lot of jffs adn jffs/mtd discussion on
> > the MTD list.
> >
> > Decoupling the two mail lists may indirectly help improve the
> > MTD/mtd-clent (JFFS2,YAFFS,Char-IO/Block-IO) API by focusing
> > more on the abstract interface and less on application specifics.
> >
> <stress>IMO<\stress>, the list is very low-volume to split it.
> Personally I have no problems seeing discussions of things to which I am
> not involved.
But actual MTD issues seem to get ignored, perhaps because the list is
so swampped with JFFS issues.
At least I think that's the reason I was completely ignored when I
posted (twice) about a bug with AMD 29LV800 parts (and thus gave
up)...
--> Steve
next prev parent reply other threads:[~2005-04-20 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 13:40 Suggestion: Give JFFS its own mail list Ian McDonnell
2005-04-20 13:59 ` Josh Boyer
2005-04-20 19:30 ` Charles Manning
2005-04-20 20:08 ` Josh Boyer
2005-04-20 20:27 ` Nicolas Pitre
2005-04-20 20:41 ` Josh Boyer
2005-04-20 20:49 ` Nicolas Pitre
2005-04-20 21:03 ` Josh Boyer
2005-04-20 14:23 ` Artem B. Bityuckiy
2005-04-20 14:39 ` Steve Wahl [this message]
2005-04-20 14:49 ` Artem B. Bityuckiy
2005-04-20 15:28 ` Josh Boyer
2005-04-20 15:28 ` Nicolas Pitre
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=20050420143958.GI1915@qlogic.com \
--to=steve.wahl@qlogic.com \
--cc=dedekind@infradead.org \
--cc=ian@brightstareng.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.