From: Matt Porter <mporter@kernel.crashing.org>
To: Stephen Rothwell <sfr@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: New mailing list specifically for embedded PowerPC development
Date: Fri, 24 Sep 2004 09:48:58 -0700 [thread overview]
Message-ID: <20040924094858.A4823@home.com> (raw)
In-Reply-To: <20040923164655.0472a8b9.sfr@ozlabs.org>; from sfr@ozlabs.org on Thu, Sep 23, 2004 at 04:46:55PM +1000
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 need further guidelines on utilization of these lists. If embedded
discussions are on linuxppc-embedded and general development discussions
are on linuxppc-dev, then where do pmac-specific discussions belong?
They certainly don't belong on linuxppc-dev since that is a specific
class of machines that not everybody has interest in and generates
a lot of traffic.
Also, where do I post patches? I typically try to copy lkml and
linuxppc-dev. Can we establish that all patches go to linuxppc-dev
regardless of general/embedded/pmac? If not, it seems we'll have
to divide patches up into the generic portion that affects everybody
for linuxppc-dev and then the embedded/pmac portion to go elsewhere.
That would be real waste and make it difficult to follow a patch
set if it were split among lists with differing subscriber bases.
Of course, if we send patches to linuxppc-dev for embedded/pmac specific
items, then that guarantees the generation of discussion outside the
stated scope of the list when people have objection/concerns about a
patch.
I personally feel that the split is unnecessary, but obviously others
had strong feelings so I'm not going to needlessly object any longer.
The most important thing at this point is to provide a bit more detail
on the lists...and probably add a linuxppc-pmac list. :)
-Matt
next prev parent reply other threads:[~2004-09-24 16:49 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
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 [this message]
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=20040924094858.A4823@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@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).