From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Mohammad Sadegh Sadri" <mamsadegh@hotmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Why did you merge two mailing lists?
Date: Tue, 6 Jan 2009 07:38:16 -0700 [thread overview]
Message-ID: <fa686aa40901060638y50702717s78b883f099fc912c@mail.gmail.com> (raw)
In-Reply-To: <BLU144-W67465C9F30727CFAF5938B2DE0@phx.gbl>
On Tue, Jan 6, 2009 at 2:26 AM, Mohammad Sadegh Sadri
<mamsadegh@hotmail.com> wrote:
> Hi All,
>
> First i should say thanks for your efforts and managing the mailing lists,
> it is great work and i know that well.
> I can not understand the reason of merging PPC-embedded and PPC devel
> mailing lists and as you see there are many people just interested in ppc
> embedded and messages there. they do not have any interest in what is going
> on in ppc devel.
If you were only following linuxppc-embedded, then you were missing
most of the embedded traffic. It has been a long time that most
embedded related messages have been going to linuxppc-dev instead of
linuxppc-embedded.
> For me, i was interested to read messages regarding Xilinx embedded powerpc
> core. I was just wanted to be informed about new patches, new changes, new
> drivers and so. and I think this is the same for many of the members of ppc
> embedded since Xilinx disscussion has been always one of the most active
> ones in that mailing list.
Yes, but even that is misleading. Sure most of the traffic on
linuxppc-embedded was xilinx traffic; but even more xilinx traffic is
on linuxppc-dev. Following only linuxppc-embedded doesn't give you
the whole picture.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2009-01-06 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-06 9:26 Why did you merge two mailing lists? Mohammad Sadegh Sadri
2009-01-06 11:49 ` Josh Boyer
2009-01-06 14:38 ` Grant Likely [this message]
2009-01-06 14:40 ` Grant Likely
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=fa686aa40901060638y50702717s78b883f099fc912c@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=mamsadegh@hotmail.com \
/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).