From: Jeremy Kerr <jk@ozlabs.org>
To: linuxppc64-dev@ozlabs.org, linuxppc-dev@ozlabs.org
Subject: Re: merge these lists?
Date: Tue, 7 Feb 2006 14:45:45 +1100 [thread overview]
Message-ID: <200602071445.45805.jk@ozlabs.org> (raw)
In-Reply-To: <17384.5875.790692.127762@cargo.ozlabs.ibm.com>
Paul,
> If we do this, we would set up the new list with the union of the
> subscribers of the old lists, and make emails sent to linuxppc-dev
> and linuxppc64-dev go to the new list, so it should be painless.
>
> Thoughts? Comments? Objections?
How about the patchwork lists? Should I look at merging those too?
Jeremy
next prev parent reply other threads:[~2006-02-07 3:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 3:41 merge these lists? Paul Mackerras
2006-02-07 3:45 ` Jeremy Kerr [this message]
2006-02-07 4:12 ` Olof Johansson
2006-02-07 4:29 ` Michael Ellerman
2006-02-07 14:36 ` Kumar Gala
2006-02-07 10:56 ` Christoph Hellwig
2006-02-07 14:35 ` Kumar Gala
2006-02-07 16:43 ` Linas Vepstas
2006-02-08 0:01 ` Stephen Rothwell
2006-02-08 0:07 ` Membership stats (Was: Re: merge these lists?) Stephen Rothwell
2006-02-24 16:34 ` Kumar Gala
2006-02-28 22:51 ` Paul Mackerras
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=200602071445.45805.jk@ozlabs.org \
--to=jk@ozlabs.org \
--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).