All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cort Dougan <cort@fsmlabs.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Support for Arctic platform (405LP based)
Date: Sun, 15 Dec 2002 12:15:26 -0700	[thread overview]
Message-ID: <20021215121526.M30941@duath.fsmlabs.com> (raw)
In-Reply-To: <20021213151808.GI19456@opus.bloom.county>; from trini@kernel.crashing.org on Fri, Dec 13, 2002 at 08:18:08AM -0700


How about killing the _2_4_devel tree?  When I created it I want it to be a
playground for stabilizing then moving things over to 2_4 failry quickly.
It seems to have become the defacto "want board X, you better use
_2_4_devel" tree.

When I went looking for a working 4xx tree recently I had to write a script
that would go through the last year of changesets in _2_4 and _2_4_devel
and try to build them then stick the result into a file.  That ran for 7
days on a 2.0Ghz Dual x86.  Then, that only gave me a list of building
trees.  Knowing that there's only 1 tree would be much easier!

I'll send you some wonderful New Mexico wine in exchange for your efforts!

} One of my goals for winter break is to try and make the _devel tree less
} divergent, at least w.r.t. 'classic' PPCs.  I'm not sure if 4xx support
} is in a stage yet that Paul is happy to move it to the _2_4 tree and
} then on to Marcelo yet.
}
} --
} Tom Rini (TR1265)
} http://gate.crashing.org/~trini/
}

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

  parent reply	other threads:[~2002-12-15 19:15 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 [this message]
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             ` Support for Arctic platform (405LP based) Cort Dougan
2002-12-16 20:13               ` PPC Tree structures (Was, at some point: Re: Support for Arctic platform (405LP based)) 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=20021215121526.M30941@duath.fsmlabs.com \
    --to=cort@fsmlabs.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.