From: "Timur Tabi" <timur@freescale.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Merge linuxppc-embedded with linuxppc-dev
Date: Tue, 23 Sep 2008 10:01:32 -0500 [thread overview]
Message-ID: <ed82fe3e0809230801o7f944983kc57da958d851de3b@mail.gmail.com> (raw)
In-Reply-To: <4BD90B25-9269-4C53-900D-33D8046DBDFE@freescale.com>
> I also vote to kill the separate embedded list. It has such low traffic,
> and it seems like a lot of messages end up cross-posted to linuxppc-dev,
> anyway.
I also agree that we should kill linuxppc-embedded.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-09-23 15:01 UTC|newest]
Thread overview: 12+ 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
2008-09-22 22:20 ` Grant Likely
2008-09-25 3:15 ` Li Yang
2008-09-22 23:09 ` Jeremy Kerr
2008-09-22 23:34 ` Kumar Gala
2008-09-23 4:53 ` Wolfram Sang
2008-09-23 14:55 ` Koss, Mike (Mission Systems)
2008-09-23 14:58 ` Becky Bruce
2008-09-23 15:01 ` Timur Tabi [this message]
2008-09-24 7:29 ` Martyn Welch
[not found] <mailman.1665.1222182678.3127.linuxppc-embedded@ozlabs.org>
2008-09-23 15:19 ` Wright, Chuck
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=ed82fe3e0809230801o7f944983kc57da958d851de3b@mail.gmail.com \
--to=timur@freescale.com \
--cc=linuxppc-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).