From: Brian Waite <linwoes@gmail.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: New mailing list specifically for embedded PowerPC development
Date: Thu, 23 Sep 2004 20:31:44 -0400 [thread overview]
Message-ID: <36b714c80409231731257ca5d0@mail.gmail.com> (raw)
In-Reply-To: <20040923233035.GH27238@smtp.west.cox.net>
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 and everyone on dev usually ends up on
embedded. 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.
Thanks
Brian
On Thu, 23 Sep 2004 16:30:35 -0700, Tom Rini <trini@kernel.crashing.org> wrote:
> On Thu, Sep 23, 2004 at 04:46:55PM +1000, Stephen Rothwell wrote:
>
> > Hi all,
> >
> > After some representations, I have created linuxppc-embedded@ozlabs.org
> > for the discussion of all things to do with the development of Linux on
> > embedded PowerPC platforms.
> >
> > General Linux on PowerPC development discussions should, of course, remain
> > on this list.
> >
> > I hope noone feels slighted :-)
>
> Could we please not do this? IMHO, it's better to keep everyone on one
> list. Less cross posting, more communication and all of that. Thanks.
> :)
>
> --
> Tom Rini
> http://gate.crashing.org/~trini/
>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
>
>
>
next prev parent reply other threads:[~2004-09-24 0:38 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 [this message]
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
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=36b714c80409231731257ca5d0@mail.gmail.com \
--to=linwoes@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=trini@kernel.crashing.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).