linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: linuxppc-embedded is no more
Date: Thu, 1 Jan 2009 16:51:48 -0700	[thread overview]
Message-ID: <fa686aa40901011551o69d7432ald4bd9e3d0bcc4c43@mail.gmail.com> (raw)
In-Reply-To: <20090102103312.924a9696.sfr@canb.auug.org.au>

On Thu, Jan 1, 2009 at 4:33 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> I have removed the linuxppc-embedded mailing list and subscribed all the
> members of that list to linuxppc-dev

... and there was much rejoicing!!!

Thanks,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

      reply	other threads:[~2009-01-01 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-01 23:33 linuxppc-embedded is no more Stephen Rothwell
2009-01-01 23:51 ` 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=fa686aa40901011551o69d7432ald4bd9e3d0bcc4c43@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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).