Suggestion: Give JFFS its own mail list.

Suggestion: Give JFFS its own mail list.

[Ian McDonnell]

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.

-ian

Re: Suggestion: Give JFFS its own mail list.

[Josh Boyer]

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?

It already has one.  jffs-dev@axis.com

josh

Re: Suggestion: Give JFFS its own mail list.

[Charles Manning]

On Thursday 21 April 2005 01:59, Josh Boyer 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?
>
> It already has one.  jffs-dev@axis.com
>
> josh

Then JFFSx postings to mtd should be labelled OT and sent to jffs-dev

I would like to monitor mtd (as part of my YAFFS work), but I'd rather not 
get all the JFFSx stuff.

-- Charles

Re: Suggestion: Give JFFS its own mail list.

[Josh Boyer]

On Thu, 2005-04-21 at 07:30 +1200, Charles Manning wrote:
> On Thursday 21 April 2005 01:59, Josh Boyer 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?
> >
> > It already has one.  jffs-dev@axis.com
> >
> > josh
> 
> Then JFFSx postings to mtd should be labelled OT and sent to jffs-dev

I guess I don't disagree, but it'll take enforcement from everyone to
make that happen.

> I would like to monitor mtd (as part of my YAFFS work), but I'd rather not 
> get all the JFFSx stuff.

Maybe another reason that the existing JFFSx list isn't used is because
it's off on some non-infradead server.  People probably see that
everything else is on *.infradead.org somewhere and just use the MTD
list for that reason.

If we could figure out a way to preserve all the archives, perhaps we
could move the JFFSx list onto lists.infradead.org.  David, thoughts?

josh

Re: Suggestion: Give JFFS its own mail list.

[Nicolas Pitre]

On Wed, 20 Apr 2005, Josh Boyer wrote:

> Maybe another reason that the existing JFFSx list isn't used is because
> it's off on some non-infradead server.  People probably see that
> everything else is on *.infradead.org somewhere and just use the MTD
> list for that reason.
> 
> If we could figure out a way to preserve all the archives, perhaps we
> could move the JFFSx list onto lists.infradead.org.  David, thoughts?

Is it worth the trouble?

It's not like if this very list was high traffic.


Nicolas

Re: Suggestion: Give JFFS its own mail list.

[Josh Boyer]

On Wed, 2005-04-20 at 16:27 -0400, Nicolas Pitre wrote:
> On Wed, 20 Apr 2005, Josh Boyer wrote:
> 
> > Maybe another reason that the existing JFFSx list isn't used is because
> > it's off on some non-infradead server.  People probably see that
> > everything else is on *.infradead.org somewhere and just use the MTD
> > list for that reason.
> > 
> > If we could figure out a way to preserve all the archives, perhaps we
> > could move the JFFSx list onto lists.infradead.org.  David, thoughts?
> 
> Is it worth the trouble?
> 
> It's not like if this very list was high traffic.

If it's not a lot of trouble, I don't see why we wouldn't preserve the
archives.  People do search them when they can find them [1].  But if
it's going to take more than a couple hours, then maybe you're right and
it doesn't really matter.

Along the same lines, JFFSx might benefit from it's own homepage as
opposed to a few references on the linux-mtd page.  However, both the
new list and a new website require admin and upkeep which is why I was
asking David what his thoughts were.  Ultimately, it's his machines and
time that are required if they are to be on infradead.org.

josh

[1] I just noticed that a link to the existing jffs-dev mailing list
seems to be missing from the linux-mtd homepage.  This should probably
be corrected.

Re: Suggestion: Give JFFS its own mail list.

[Nicolas Pitre]

On Wed, 20 Apr 2005, Josh Boyer wrote:

> On Wed, 2005-04-20 at 16:27 -0400, Nicolas Pitre wrote:
> > On Wed, 20 Apr 2005, Josh Boyer wrote:
> > 
> > > Maybe another reason that the existing JFFSx list isn't used is because
> > > it's off on some non-infradead server.  People probably see that
> > > everything else is on *.infradead.org somewhere and just use the MTD
> > > list for that reason.
> > > 
> > > If we could figure out a way to preserve all the archives, perhaps we
> > > could move the JFFSx list onto lists.infradead.org.  David, thoughts?
> > 
> > Is it worth the trouble?
> > 
> > It's not like if this very list was high traffic.
> 
> If it's not a lot of trouble, I don't see why we wouldn't preserve the
> archives.

I meant moving/splitting the lists around.


Nicolas

Re: Suggestion: Give JFFS its own mail list.

[Josh Boyer]

On Wed, 2005-04-20 at 16:49 -0400, Nicolas Pitre wrote:
> On Wed, 20 Apr 2005, Josh Boyer wrote:
> 
> > On Wed, 2005-04-20 at 16:27 -0400, Nicolas Pitre wrote:
> > > On Wed, 20 Apr 2005, Josh Boyer wrote:
> > > 
> > > > Maybe another reason that the existing JFFSx list isn't used is because
> > > > it's off on some non-infradead server.  People probably see that
> > > > everything else is on *.infradead.org somewhere and just use the MTD
> > > > list for that reason.
> > > > 
> > > > If we could figure out a way to preserve all the archives, perhaps we
> > > > could move the JFFSx list onto lists.infradead.org.  David, thoughts?
> > > 
> > > Is it worth the trouble?
> > > 
> > > It's not like if this very list was high traffic.
> > 
> > If it's not a lot of trouble, I don't see why we wouldn't preserve the
> > archives.
> 
> I meant moving/splitting the lists around.

Oh :).

Personally, the JFFSx stuff in the MTD list doesn't bother me.  I was
just offering up an idea that might help those who are bothered.  I
don't really have any convictions about it one way or another.

josh

Re: Suggestion: Give JFFS its own mail list.

[Artem B. Bityuckiy]

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.

Re: Suggestion: Give JFFS its own mail list.

[Steve Wahl]

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

Re: Suggestion: Give JFFS its own mail list.

[Artem B. Bityuckiy]

On Wed, 2005-04-20 at 09:39 -0500, Steve Wahl wrote:
> > <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)...

Nonetheless I have had no problems to be subscribed to several lists if
the current one would be split. :-)

-- 
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.

Re: Suggestion: Give JFFS its own mail list.

[Josh Boyer]

On Wed, 2005-04-20 at 09:39 -0500, Steve Wahl wrote:
> 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)...

Hm, I don't think that's the reason.  I read your posts, and they made
sense to me.  But I don't have any similar hardware, and can't confirm,
debug, or otherwise make a useful contribution.  That may be more of a
reason for nobody responding.

Another reason is that people are generally busy and just don't have
time to read the list.  We aren't ignoring you on purpose, so please
don't give up.

Patches always get more attention too :).

josh

Re: Suggestion: Give JFFS its own mail list.

[Nicolas Pitre]

On Wed, 20 Apr 2005, Steve Wahl wrote:

> But actual MTD issues seem to get ignored, perhaps because the list is
> so swampped with JFFS issues.

I really doubt that.  I don't think it would be any different even with 
JFFS issues being moved elsewhere.

> 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)...

If you were ignored that's probably because no one currently has a clue 
at hand to give you.  Spliting the list won't change anything to that.


Nicolas