linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: ppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: Reminder: removal of APUS and Gemini still pending
Date: Sat, 17 Sep 2005 21:48:52 +0200	[thread overview]
Message-ID: <432C7324.9070203@linux-m68k.org> (raw)
In-Reply-To: <15A1D026-00E3-4652-ABA5-9A8B8517A2CA@freescale.com>

Hi,

Kumar Gala wrote:

> This is a reminder email to all those that care that APUS and Gemini 
> configs are still not building in the kernel.  They are still  scheduled
> to be removed after the release of 2.6.15.

Regarding APUS: with the current rate of changes I simply don't have the
time to catch up right now. What's the game plan here? If I miss the
deadline, I have to start from scratch?

bye, Roman

  parent reply	other threads:[~2005-09-17 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 16:36 Reminder: removal of APUS and Gemini still pending Kumar Gala
2005-09-17 14:09 ` Simon Richter
2005-09-18 22:01   ` Paul Mackerras
2005-09-19  9:10     ` Christoph Hellwig
2005-09-17 19:48 ` Roman Zippel [this message]
2005-09-18 10:27   ` Simon Richter

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=432C7324.9070203@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=kumar.gala@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).