From: Cort Dougan <cort@fsmlabs.com>
To: K?ri Dav??sson <kd@flaga.is>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: linuxppc2.5 tree
Date: Sat, 17 Feb 2001 19:27:17 -0700 [thread overview]
Message-ID: <20010217192716.H18493@ftsoj.fsmlabs.com> (raw)
In-Reply-To: <20010217150538.A22215@BigTits.flaga>; from kd@flaga.is on Sat, Feb 17, 2001 at 03:05:38PM +0000
We upgraded the server and are still bringing services back. Rsync is on
the list, but isn't a priority. For now, I'd suggest using BK.
} As I understand be reading the mailing list archives, the linuxppc_2_5 tree at
} bitkeeper.fsmlabs.com is where most of the development for the MPC8xx CPU is
} happening, especially USB stuff.
}
} bitkeeper.fsmlabs.com only seem to export them to the "bitkeeper" tools which
} mean I am not able to download them. Is there a way to get the linuxppc_2_5
} tree by any other means, or any other place?
}
} The rsync method also seem to be "dead", although the firewall here might
} (likely) also be blocking of the rsync ports as well as the 500? series of
} ports. This leaves only ftp, http, and email as a possible transport method.
}
} Thanks,
}
} K.D.
}
}
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-02-18 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 15:05 linuxppc2.5 tree K?ri Dav??sson
2001-02-18 2:27 ` Cort Dougan [this message]
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=20010217192716.H18493@ftsoj.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=kd@flaga.is \
--cc=linuxppc-embedded@lists.linuxppc.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).