From: Roland Dreier <roland@topspin.com>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Does 'Bitkeeper' work according to the 'kernel sources' link @ pp cpenguin.org
Date: 23 Jan 2003 12:21:07 -0800 [thread overview]
Message-ID: <52d6mnzkgc.fsf@topspin.com> (raw)
In-Reply-To: <995FF289C9D69747A09E42992644595405B2361D@penguin.adic.com>
brian> This is my first time using bk. I bk'ed linuxppc_2_4, but
brian> it appears that the whole thing does not get
brian> downloaded. For example, the "scripts/lxdialog" directory
brian> in the kernel source tree does not have any contents other
brian> than the SCCS directory. I find this is a consistent
brian> problem with a smattering of diretories within the kernel
brian> source tree. I cannot successfully execute "make
brian> menuconfig" and am stumped.
Do "bk -r co" in your bk tree after your "bk clone" to check out the
actual source files.
- Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-23 20:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 20:03 Does 'Bitkeeper' work according to the 'kernel sources' link @ pp cpenguin.org brian.auld
2003-01-23 20:21 ` Roland Dreier [this message]
2003-01-23 20:29 ` Leonardo Pereira Santos
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=52d6mnzkgc.fsf@topspin.com \
--to=roland@topspin.com \
--cc=brian.auld@adic.com \
--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 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.