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:40:47 -0700 [thread overview]
Message-ID: <fa686aa40901060640w29e7ad12jfb08e5874c050bd3@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:
> any how i understand that there is no way to go back where we were
> previously, and so i should just say thanks, and that i have to unsubscribe
> from the new mailing list althougth i know there would be emails in which
> i'll be interested.
Alternately, you could also create for yourself a filter that drops
all linuxppc-dev messages that don't contain the words "xilinx",
"virtex" or similar. Just about all email clients provide a method
for filtering.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-01-06 14:40 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
2009-01-06 14:40 ` Grant Likely [this message]
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=fa686aa40901060640w29e7ad12jfb08e5874c050bd3@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).