linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: linuxppc-embedded@lists.linuxppc.org
Subject: the door is closing for 2.4
Date: Thu, 4 Dec 2003 11:34:04 +1100	[thread overview]
Message-ID: <16334.33020.624995.521330@cargo.ozlabs.ibm.com> (raw)


Guys,

Marcelo has announced that as of 2.4.25, the official 2.4 tree is
going into maintenance-only mode.  There is still a lot of stuff in
the linuxppc-2.4 and linuxppc_2_4_devel trees which hasn't gone into
the official 2.4 tree.  Most of that is board ports for various
embedded boards, and for many of those boards, it's not clear whether
anyone cares whether they are supported by the official 2.4 or not.

So if you have a board that you want to see supported by the official
2.4 tree, and it isn't already, let me know.  I will need someone to
commit to maintaining the port on an ongoing basis before I send it to
Marcelo, though.

We also need people to start moving their embedded board ports to
2.6, along with all the related device drivers, etc.  We are already
past the point where new development should all be done in 2.5/2.6.

Paul.


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2003-12-04  0:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04  0:34 Paul Mackerras [this message]
2003-12-04  9:16 ` the door is closing for 2.4 Pantelis Antoniou
2003-12-04 13:55   ` Dan Malek
2003-12-04 15:06     ` Pantelis Antoniou
2003-12-04 15:34       ` Dan Malek
2003-12-05  7:24         ` Pantelis Antoniou
2003-12-05 18:54           ` Dan Malek
2003-12-04  9:47 ` Stefan Roese
2003-12-05  0:08 ` Kumar Gala
2004-01-12  5:30   ` Paul Mackerras
2003-12-10 15:38 ` Hubert Figuiere
2003-12-10 16:55   ` Tom Rini
2003-12-10 16:57     ` Hubert Figuiere
2003-12-10 19:19       ` Tom Rini

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=16334.33020.624995.521330@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-embedded@lists.linuxppc.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).