From: "Mike Frysinger" <vapier.adi@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Jeremy Kerr <jk@ozlabs.org>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
linux-embedded@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: Merge linuxppc-embedded with linuxppc-dev
Date: Mon, 22 Sep 2008 18:11:57 -0400 [thread overview]
Message-ID: <8bd0f97a0809221511v1aba47eemb1630f7e64412e4@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40809221508q22e23e53s2140b17de83bcb1a@mail.gmail.com>
On Mon, Sep 22, 2008 at 18:08, Grant Likely <grant.likely@secretlab.ca> wrote:
> Jeremy,
>
> Can we eliminate the linuxppc-embedded mailing list and merge it with
> linuxppc-dev? I don't think we need two separate lists anymore and
> patches to linuxppc-embedded don't always get dealt with.
>
> Anyone have any objections to eliminating linuxppc-embedded?
you sent this e-mail to "linux-embedded" instead of "linuxppc-embedded"
-mike
next prev parent reply other threads:[~2008-09-22 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 22:08 Merge linuxppc-embedded with linuxppc-dev Grant Likely
2008-09-22 22:11 ` Mike Frysinger [this message]
2008-09-22 22:20 ` Grant Likely
2008-09-22 23:09 ` Jeremy Kerr
2008-09-22 23:34 ` Kumar Gala
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=8bd0f97a0809221511v1aba47eemb1630f7e64412e4@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=jk@ozlabs.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).