linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
	<linuxppc-dev@lists.linuxppc.org>
Subject: Re: kernel ftp ?
Date: Mon, 16 Jul 2001 20:29:10 +0200	[thread overview]
Message-ID: <20010716182910.21970@smtp.adsl.oleane.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107161852360.10461-100000@opal.biophys.uni-duesseldorf.de>


>
>> Paul no longer maintains his own tree, his work is directly merged
>> in either bk _2_4 or _2_4_devel now.
>
>Which are hosted by montavista:
>rsync -avz --delete source.mvista.com::linuxppc_2_4 <directory>
>
>for the 'stable' 2.4 tree.

Those are mirrors, the main repository is hosted by bitmover
(ppc.bitkeeper.com). But those mirrors should work fine as well..

Ben.


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

  reply	other threads:[~2001-07-16 18:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-15 14:10 kernel ftp ? Giuliano Pochini
2001-07-16  4:22 ` Steven Hanley
2001-07-16  7:38   ` Benjamin Herrenschmidt
2001-07-16 16:54     ` Michael Schmitz
2001-07-16 18:29       ` Benjamin Herrenschmidt [this message]
2001-07-16 18:01         ` Michael Schmitz
2001-07-16 18:12           ` Larry McVoy
2001-07-16 18:38             ` Michael Schmitz
2001-07-16 18:57               ` Larry McVoy
2001-07-22 20:30                 ` Troy Benjegerdes
2001-07-22 22:15                   ` Larry McVoy
2001-07-22 23:32                     ` Lars Magne Ingebrigtsen
2001-07-23  7:07                     ` Geert Uytterhoeven
2001-07-23  9:28                       ` Timothy A. Seufert
  -- strict thread matches above, loose matches on Subject: below --
2001-07-23  9:44 Zehetbauer Thomas
2001-07-23 15:38 ` Larry McVoy
2001-07-23 16:44   ` Troy Benjegerdes

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=20010716182910.21970@smtp.adsl.oleane.com \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=schmitz@opal.biophys.uni-duesseldorf.de \
    /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).