linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Support for Arctic platform (405LP based)
Date: Mon, 16 Dec 2002 12:49:31 -0700	[thread overview]
Message-ID: <20021216124931.B9431@duath.fsmlabs.com> (raw)
In-Reply-To: <20021216150442.GJ6095@opus.bloom.county>; from trini@kernel.crashing.org on Mon, Dec 16, 2002 at 08:04:42AM -0700


} I'm not sure how that would stop the growth of the '_devel' tree, it
} would just split it up into 4xx, and everything else.  And my goal of
} the new few weeks is to try and move everything that's not 4xx that I
} can get my hands on to test into the _2_4 tree.  I'm not sure just how
} much of that I'll actually be able to do, but I'm going to try.

There would be no _devel tree in that case.  They'd all be based on
Marcelo's so moving back and forth would be easier.  There would also be
more trees and smaller patches.

Right now, if you want an embedded board to boot your only chance is to try
the wildly divergent - likely unstable - _devel tree.  Having something
like this would be much nicer:


marcelo ---> linuxppc_2_4 --- linuxppc_2_4_4xx
                  |                 |
		  |		    ---> linuxppc_2_4_4xx_walnut
		  |		    |
		  |		    ---> linuxppc_2_4_4xx_crazystuff
		  |		    |
		  |		    ---> linuxppc_2_4_4xx_some_whacky_port
		  |
		  |
		  |
		  |---> linuxppc_2_4_something

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

  parent reply	other threads:[~2002-12-16 19:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  4:36 Support for Arctic platform (405LP based) David Gibson
2002-12-13  4:51 ` Cort Dougan
2002-12-13 14:26   ` Gary Thomas
2002-12-13 15:16     ` Tom Rini
2002-12-13 16:35       ` Tom Rini
2002-12-16 20:39         ` linuxppc-commit mailing list Hollis Blanchard
2002-12-13 15:18   ` Support for Arctic platform (405LP based) Tom Rini
2002-12-13 15:28     ` Matt Porter
2002-12-15 19:15     ` Cort Dougan
2002-12-15 19:51       ` Tom Rini
2002-12-15 23:43       ` Paul Mackerras
2002-12-16  0:41         ` Cort Dougan
2002-12-16 15:04           ` Tom Rini
2002-12-16 15:08             ` Tom Rini
2002-12-16 16:25               ` Discovery II (was Re: Support for Arctic platform (405LP based)) Roland Dreier
2002-12-16 12:45                 ` Mark A. Greer
2002-12-16 19:49                   ` Roland Dreier
2002-12-16 14:33                     ` Mark A. Greer
2002-12-18 11:01                   ` Rabeeh Khoury
2002-12-16 19:49             ` Cort Dougan [this message]
2002-12-16 20:13               ` PPC Tree structures (Was, at some point: " Tom Rini
2002-12-16 20:13                 ` Cort Dougan
2002-12-16 20:36                   ` Tom Rini
2002-12-19 18:06                 ` PPC Tree structures (Was, at some point: " Cort Dougan
2002-12-19 18:17                   ` Tom Rini
2002-12-16  1:43         ` Support for Arctic platform (405LP based) David Gibson
2002-12-16 15:02         ` Tom Rini
2002-12-13 19:25 ` Todd Poynor
2002-12-15  7:35   ` David Gibson
2002-12-16  1:58     ` David Gibson

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=20021216124931.B9431@duath.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=paulus@samba.org \
    --cc=trini@kernel.crashing.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).