From: Tom Rini <trini@kernel.crashing.org>
To: Hollis Blanchard <hollis@penguinppc.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: New mailing list specifically for embedded PowerPC development
Date: Thu, 23 Sep 2004 20:23:00 -0700 [thread overview]
Message-ID: <20040924032300.GA2107@smtp.west.cox.net> (raw)
In-Reply-To: <29D00F8B-0DC8-11D9-A0FB-000A95A0560C@penguinppc.org>
[-- Attachment #1: Type: text/plain, Size: 1660 bytes --]
On Thu, Sep 23, 2004 at 08:22:13PM -0500, Hollis Blanchard wrote:
> I could go either way, but I think I'm leaning towards separate lists.
>
> On Sep 23, 2004, at 7:31 PM, Brian Waite wrote:
>
> >I have to agree with Tom. After trying desperatly to keep up in the
> >time of too many lists, I would really like to keep the lists to a
> >minimum. If one archive can be searched for answers, life becomes much
> >easier. It becomes useless to split the lists as everyone on embedded
> >needs to be on dev eventually
>
> Probably true...
>
> >and everyone on dev usually ends up on embedded.
>
> I think this is the difference. Hackers with an iBook don't necessarily
> know or care about issues in the drivers for this year's new embedded
> SoC. In fact they probably don't. They probably care about cpufreq, and
> 3D acceleration, and why their laptop doesn't wake up when it goes to
> sleep.
>
> >It also helps head off rat holes where 2 groups on different
> >lists solve the same prolem differently. I vote for one list, but the
> >is just me.
>
> 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.
Look at the flip side of things. There's the everything developer
folks, who really need to be on all of the lists, the 'embedded' folks,
and the apple folks. We used to have linux-pmac, but that kinda evolved :)
If someone suggested we have "linuxppc-dev" and "linuxppc-pmac" I assume
that other folks would complain they have to be on two lists...
--
Tom Rini
http://gate.crashing.org/~trini/
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-09-24 3:23 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 [this message]
2004-09-24 5:52 ` Dan Malek
2004-09-24 16:41 ` Tom Rini
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=20040924032300.GA2107@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=hollis@penguinppc.org \
--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).