From: Matt Porter <mporter@kernel.crashing.org>
To: linuxppc-dev@ozlabs.org, linuxppc-embedded@ozlabs.org
Subject: [NOTICE] List description/usage changes
Date: Mon, 27 Sep 2004 08:27:59 -0700 [thread overview]
Message-ID: <20040927082759.E25675@home.com> (raw)
For everybody already on the lists that aren't going to see the
changes on the mailman subscription pages...this is for you.
Summary: ppc32 embedded discussion belong on -embedded. Everything
else ppc32 on -dev.
See the following text that sfr adopted to clarify list usage:
------------
linuxppc-dev
------------
This is the Linux on PowerPC developers' mailing list. It is
free and open to all those interested in development of Linux
on PowerPC hardware, but discussions/patches should pertain to
software development for the kernel core ppc32 support and
CHRP/Pmac/PReP platforms. Any discussions/patches regarding
embedded procesoors/platforms should be directed to the
linuxppc-embedded list.
Patches are welcomed, but please refrain from posting excessively
large ones (40K is currently the limit for the entire message).
Large patches should be made available at an accessible FTP or
web site and the URL posted to this list. The list owner reserves
the right to implement filtering of list messages, unsubscribe
offenders, and/or otherwise prevent posting of messages to enforce
the list charter.
-----------------
linuxppc-embedded
-----------------
This is the Linux on PowerPC embedded developers' mailing list.
It is free and open to all those interested in development
of Linux on embedded PowerPC hardware, but discussions/patches
should pertain to software development for the kernel core ppc32
embedded processor support and any driver/chip/board support for
ppc32 based embedded systems. Any discussions/patches regarding
generic core ppc32 support should be directed to the linuxppc-dev
list.
Patches are welcomed, but please refrain from posting excessively
large ones (40K is currently the limit for the entire message).
Large patches should be made available at an accessible FTP or
web site and the URL posted to this list. The list owner reserves
the right to implement filtering of list messages, unsubscribe
offenders, and/or otherwise prevent posting of messages to enforce
the list charter.
reply other threads:[~2004-09-27 15:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040927082759.E25675@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc-embedded@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).