From: Stephen Rothwell <sfr@canb.auug.org.au>
To: ppc64-dev <linuxppc64-dev@ozlabs.org>
Cc: linuxppc-dev@ozlabs.org
Subject: merging lists
Date: Tue, 21 Mar 2006 10:34:09 +1100 [thread overview]
Message-ID: <20060321103409.48b10200.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
Hi all,
I am bout the merge the two mailing lists (so that only linuxppc-dev will
continue). To do this, I will subscribe all the members of the
linuxppc64-dev lists that are not members of linuxppc-dev to the second
list. If you are subscribed under different addresses to the two
different lists, you will start getting two copies of everything until you
unsubscribe one of your addresses.
There may be a small amount of disruption, I apologise in advance.
I will redirect the linuxppc64-dev mail addresses to the linucppc-dev ones
and the archives and patchwork will remain available at their current
addresses.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 191 bytes --]
reply other threads:[~2006-03-20 23:34 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=20060321103409.48b10200.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-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).