public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel•crashing.org>
To: Stefan Jeglinski <jeglin@4pi•com>
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: 2.5 development
Date: Tue, 26 Feb 2002 09:13:03 -0700	[thread overview]
Message-ID: <20020226161303.GA3849@opus.bloom.county> (raw)
In-Reply-To: <p05100305b8a15d9b9ab6@[63.220.231.138]>


On Tue, Feb 26, 2002 at 10:51:53AM -0500, Stefan Jeglinski wrote:
>
> >The linux_2_5 and linuxppc_2_5 trees are
> >dead, and I will remove them once we are sure we have all the changes
> >from linuxppc_2_5 committed to the linuxppc-2.5 tree.
>
> Will a mirror of this 2.5 tree still be available by rsync from
> source.mvista.com?

linuxppc-2.5 is currently up on rsync.

> Speaking of which, rsyncing the 2.4 tree at source.mvista.com shows
> that it is at 2.4.18-rc2. Can I take this to mean that this bk-mirror
> is also dead? If so, is there a replacement rsync source to keep up
> with the bk tree?

It'll be updated again shortly.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

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

  reply	other threads:[~2002-02-26 16:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <p05100300b8a144d7cf05@[66.26.75.241]>
2002-02-26 15:51 ` 2.5 development Stefan Jeglinski
2002-02-26 16:13   ` Tom Rini [this message]
2002-02-15 12:11 Paul Mackerras
2002-02-15 16:40 ` Tom Rini
2002-02-15 16:58 ` Larry McVoy
2002-02-15 17:01   ` Jeff Garzik
2002-02-15 17:06     ` Larry McVoy
2002-02-15 17:17     ` Larry McVoy
2002-02-15 17:32   ` Tom Rini
2002-02-15 17:33     ` Larry McVoy
2002-02-15 17:36       ` Tom Rini
2002-02-15 18:44         ` Larry McVoy
2002-02-15 18:50           ` Tom Rini
2002-02-15 23:53             ` Larry McVoy

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=20020226161303.GA3849@opus.bloom.county \
    --to=trini@kernel$(echo .)crashing.org \
    --cc=jeglin@4pi$(echo .)com \
    --cc=linuxppc-dev@lists$(echo .)linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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