From: Andreas Schwab <schwab@suse.de>
To: Christian Kujau <evil@g-house.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: linuxppc trees / BK help
Date: Tue, 27 Jan 2004 17:23:46 +0100 [thread overview]
Message-ID: <jewu7d2wdp.fsf@sykes.suse.de> (raw)
In-Reply-To: <40168C3E.7010903@g-house.de> (Christian Kujau's message of "Tue, 27 Jan 2004 17:05:18 +0100")
Christian Kujau <evil@g-house.de> writes:
> 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.
$ bk -r get
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-27 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-27 16:05 linuxppc trees / BK help Christian Kujau
2004-01-27 16:23 ` Andreas Schwab [this message]
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=jewu7d2wdp.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.