From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: New mailing list specifically for embedded PowerPC development
Date: Fri, 24 Sep 2004 09:41:46 -0700 [thread overview]
Message-ID: <20040924164146.GG2107@smtp.west.cox.net> (raw)
In-Reply-To: <DA7E9084-0DED-11D9-A74B-003065F9B7DC@embeddededge.com>
On Fri, Sep 24, 2004 at 01:52:00AM -0400, Dan Malek wrote:
>
> On Sep 23, 2004, at 9:22 PM, Hollis Blanchard wrote:
>
> >I think ultimately the problem is that the embedded list ends up
> >generating a *lot* of traffic, and that traffic ends up drowning out
> >non-embedded topics.
>
> This was the reason the list was created years ago. People got tired
> of reading my comments and few people were involved in embedded
> development at that time :-) People with no interest in embedded didn't
> want to hear about it.
I would dare say that a few years ago the embedded side was a bit
smaller than today :)
> I don't know why anyone would care if they have to subscribe to
> multiple lists to get the information they need. There isn't any need
> to cross post and I don't think this is done very much or at all. There
> have been a few times early in the -embedded days that I have taken
> topics from the embedded list to the -dev list, but this isn't necessary
> any more because the interested parties are on both.
Well, it's not exactly obvious to new people why exactly the 'dev' list
isn't for embedded development. It also helps foster the notion that
'those embedded folks just go off and do their own thing'.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2004-09-24 16:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-23 6:46 New mailing list specifically for embedded PowerPC development Stephen Rothwell
2004-09-23 23:30 ` Tom Rini
2004-09-24 0:31 ` Brian Waite
2004-09-24 1:22 ` Hollis Blanchard
2004-09-24 3:23 ` Tom Rini
2004-09-24 5:52 ` Dan Malek
2004-09-24 16:41 ` Tom Rini [this message]
2004-09-25 2:59 ` Benjamin Herrenschmidt
2004-09-25 3:01 ` Benjamin Herrenschmidt
2004-09-25 3:08 ` Owen Stampflee
2004-09-25 18:01 ` Tom Rini
2004-09-25 18:10 ` Matt Porter
2004-09-25 17:57 ` Tom Rini
2004-09-25 23:12 ` Benjamin Herrenschmidt
2004-09-25 18:08 ` Matt Porter
2004-09-24 1:07 ` Eugene Surovegin
2004-09-24 16:48 ` Matt Porter
2004-09-25 18:56 ` Matt Porter
2004-09-26 12:13 ` Stephen Rothwell
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=20040924164146.GG2107@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=dan@embeddededge.com \
--cc=linuxppc-dev@ozlabs.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).