linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev <Linuxppc-dev@ozlabs.org>
Subject: Re: [CURIOUSITY] When will we stop caring about arch/ppc?
Date: Tue, 26 Jun 2007 15:46:58 +0200	[thread overview]
Message-ID: <1ce7f225511ea3d67a63b8a4ac683e0c@kernel.crashing.org> (raw)
In-Reply-To: <1182864764.19501.7.camel@weaponx.rchland.ibm.com>

>>> But I meant adding
>>> something in the Documentation/powerpc/ directory and maybe
>>> feature-removal-schedule.txt.  Basically a written down thing in the
>>> kernel source to refer people to.
>>
>> How about this time next year -- special event at
>> the OLS PowerPC BOF :-)
>
> Heh, sounds good to me.
>
> Of course, getting stuff done in a year.... ;)

Well the arch/ppc tree is basically frozen already, all Freescale
stuff got moved over already as far as I can see, and 4xx has
started moving.  I think a year is enough, since the tree is
frozen anyway, people can resurrect stuff from older releases
if need be, no problem with deleting it.  In fact, why not do
so this year :-)  [Yeah that was a joke].


Segher

  reply	other threads:[~2007-06-26 13:46 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25 18:23 [CURIOUSITY] When will we stop caring about arch/ppc? Mark A. Greer
2007-06-25 18:40 ` Josh Boyer
2007-06-25 19:42   ` Kumar Gala
2007-06-25 20:50     ` Josh Boyer
2007-06-26  7:48       ` Segher Boessenkool
2007-06-26 13:32         ` Josh Boyer
2007-06-26 13:46           ` Segher Boessenkool [this message]
2007-06-26 13:57             ` Josh Boyer
2007-06-26 17:03             ` Arnd Bergmann
2007-06-26 18:51               ` Kumar Gala
2007-06-26 21:11               ` Vitaly Bordug
2007-06-26 17:18             ` Mark A. Greer
2007-07-03 18:29               ` Scott Wood

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=1ce7f225511ea3d67a63b8a4ac683e0c@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=jwboyer@linux.vnet.ibm.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).