From: Christian Kujau <evil@g-house.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: linuxppc trees / BK help
Date: Tue, 27 Jan 2004 17:05:18 +0100 [thread overview]
Message-ID: <40168C3E.7010903@g-house.de> (raw)
hello,
after reading the recent threads about the different ppc trees (and much
BK stuff i still have to learn) i am still wondering if there are CVS
trees from say 2.4.24-benh or linuxppc-2.5-benh available.
there is a BK2CVS gateway, but my cloning always results only in
"strange trees". as seen on http://penguinppc.org/dev/kernel.shtml i do
bk clone bk://source.mvista.com/linuxppc-2.5-benh linuxppc-2.5-benh-BK
after passing the consistency check, a sourcetree shows up but
filenames are different from normal:
evil@sheep:/data/MP3/scratch/kernel$ ls linuxppc-2.5-benh-BK/
BitKeeper Documentation SCCS arch crypto drivers fs include init
~ ipc kernel lib mm net scripts security sound usr
evil@sheep:/data/MP3/scratch/kernel$
- --> there are no files in the directory, only dirs.
evil@sheep:/data/MP3/scratch/kernel$ ls -w10 linuxppc-2.5-benh-BK/kernel/
SCCS
power
evil@sheep:/data/MP3/scratch/kernel$
yes, there are files somewhere too, e.g.
linuxppc-2.5-benh-BK/sound/pci/cs46xx/SCCS/s.dsp_spos.h
is there, but it is some kind of changelog or so. as you can imagine,
compiling fails :-(
someone there to enlighten me what´s going on here?
Thank you,
Christian.
- --
BOFH excuse #259:
Someone's tie is caught in the printer, and if anything else gets
printed, he'll be in it too.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-01-27 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 16:05 Christian Kujau [this message]
2004-01-27 16:23 ` linuxppc trees / BK help Andreas Schwab
2004-01-27 18:07 ` Christian Kujau
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=40168C3E.7010903@g-house.de \
--to=evil@g-house.de \
--cc=linuxppc-dev@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).