From: Steven Scholz <steven.scholz@imc-berlin.de>
To: linuxppc-embedded@lists.linuxppc.org
Subject: BitKeeper and linuxppc_2_4_devel
Date: Wed, 19 Sep 2001 11:36:50 +0200 [thread overview]
Message-ID: <3BA86732.363312A4@imc-berlin.de> (raw)
Hi there,
I am trying to get the latest kernel sources.
But "bk clone http://source.mvista.com/linuxppc_2_4_devel linux/"
results today (!?) in
drainErrorMsg: Unexpected response:
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Has anyone else the same problem?
BTW which one has the most recent source: ppc.bkserver.net oder
source.mvista.com???
Cheers,
Steven
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-09-19 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-19 9:36 Steven Scholz [this message]
2001-09-19 10:38 ` BitKeeper and linuxppc_2_4_devel Matt Porter
2001-09-19 14:46 ` Tom Rini
2001-09-19 14:58 ` Steven Scholz
2001-09-19 15:13 ` Steven Scholz
2001-09-19 16:43 ` Kenneth Johansson
2001-09-19 15:41 ` Matt Porter
2001-09-20 0:12 ` Tom Rini
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=3BA86732.363312A4@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--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).