From: Christian <evil@g-house.de>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: How to get the exact source code from this clone of linux tree:bitkeeper
Date: Fri, 12 Mar 2004 14:06:50 +0100 [thread overview]
Message-ID: <4051B5EA.4030502@g-house.de> (raw)
In-Reply-To: <001b01c40802$ea7e2970$3401080a@telxsi.com>
challaharikumar wrote:
> How to get the exact source code from this clone of linux tree.. Any help
> would be highly appreciated
i myself was once asking this on this list and i was told to do:
$ bk clone bk://source.mvista.com/linuxppc-2.5-benh linuxppc-2.5-benh-BK
(to fetch the linuxppc-2.5-benh tree and store it into
./linuxppc-2.5-benh-BK )
and then
$ cd linuxppc-2.5-benh-BK
$ bk -r get
although i always thought "clone" would really "clone" the tree itself...
cheers,
Christian.
--
BOFH excuse #59:
failed trials, system needs redesigned
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-03-12 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-12 7:23 How to get the exact source code from this clone of linux tree:bitkeeper challaharikumar
2004-03-12 9:04 ` Colin Leroy
2004-03-12 13:06 ` Christian [this message]
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=4051B5EA.4030502@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).