From: "Dan A. Dickey" <ddickey@charter.net>
To: "linuxppc-embedded@lists.linuxppc.org"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Latest linux-ppc sources & access method?
Date: Tue, 06 Jun 2000 21:44:42 -0500 [thread overview]
Message-ID: <393DB71A.4BBE8F29@charter.net> (raw)
Hi,
just checking to see where the latest sources are at
(Monta Vista or FSMLabs?) and the access method that
people use to get them. Do people generally just ftp
or http a tgz file? Of course, the preferred method
is BitKeeper; and following that anonymous CVS.
Can someone let me know where the bitkeeper daemon
for linuxppc development lives at? And whatever
information I need to know in order to clone a
repository. (Yes, I have bitkeeper and have been
using it; it works well). If someone would like
to fill in the holes, please let me know about cvs
access as well - at various places. I'll summarize
and repost whatever information I'm able to gather,
for the record.
-Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-06-07 2:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-07 2:44 Dan A. Dickey [this message]
2000-06-06 21:44 ` Latest linux-ppc sources & access method? Steve Tarr
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=393DB71A.4BBE8F29@charter.net \
--to=ddickey@charter.net \
--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).