linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: linuxppc-embedded@lists.linuxppc.org
Cc: Murray.Jensen@cmst.csiro.au, trini@kernel.crashing.org
Subject: Re: linuxppc_2_5 source tree (and others)
Date: Thu, 10 May 2001 14:40:05 -0400 (EDT)	[thread overview]
Message-ID: <200105101840.f4AIe5d413262@saturn.cs.uml.edu> (raw)


Tom Rini writes:
> On Thu, May 10, 2001 at 06:38:02PM +1000, Murray Jensen wrote:

>> Hi, I see that the linuxppc_2_5 bk tree has disappeared from fsmlabs, and
>> has been replaced with a linuxppc_2_4_devel tree. Could someone in the
>> know please post a quick update what this means, and perhaps what the
>> future holds wrt 2.4/2.5 linuxppc (embedded)?
>
> I was hoping Cort would mention this here, but 2_5 has been 'dead' for a
> while and is finally gone too.  There's still mirrors of it however.
> It will exist again, but when 2.5.0 appears and will be based off the
> linux_2_4 tree or so.  Right now 2_4_devel isn't up to date wrt 8xx/4xx, and
> some new boards 2_5 had.  I'm working on it. :)

Oh, lovely.

I'm very glad to have ignored this BitKeeper nonsense for
the most part then. I knew there was a good reason to rely
on the one true source tree from Linus. I'm not screwed like
all the people working from linuxppc_2_5 are.

On the other hand, I had to do my own PowerCore 6750 VME port
for the 2.4 kernel. That sucked. It would be nice if everyone
had the decency to submit stuff to Linus in a way that he finds
acceptable, rather than hoarding source code in obscure places
that are only accessible via non-standard non-free software.

So, how did _you_ know that 2_5 has been 'dead' for a while?

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

             reply	other threads:[~2001-05-10 18:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-10 18:40 Albert D. Cahalan [this message]
2001-05-10 18:49 ` linuxppc_2_5 source tree (and others) Tom Rini
2001-05-10 19:46   ` Albert D. Cahalan
2001-05-10 19:57     ` Cort Dougan
2001-05-10 21:24       ` Albert D. Cahalan
2001-05-10 23:11         ` Cort Dougan
2001-05-11  2:31           ` Murray Jensen
2001-05-11  3:14             ` Cort Dougan
2001-05-11  5:43               ` Murray Jensen
2001-05-10 21:44     ` Tom Rini
2001-05-13 19:33       ` Ira Weiny
2001-05-15  1:40         ` Cort Dougan
  -- strict thread matches above, loose matches on Subject: below --
2001-05-10  8:38 Murray Jensen
2001-05-10 16:10 ` Tom Rini
2001-05-10 16:24 ` Dan Malek
2001-05-10 19:33 ` Cort Dougan

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=200105101840.f4AIe5d413262@saturn.cs.uml.edu \
    --to=acahalan@cs.uml.edu \
    --cc=Murray.Jensen@cmst.csiro.au \
    --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 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).