From: Wouter Cloetens <wouter@mind.be>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: downloading source with specific changeset
Date: Mon, 12 Jan 2004 02:16:42 +0100 [thread overview]
Message-ID: <20040112011642.GI9059@roadkill.intern.mind.be> (raw)
In-Reply-To: <D73A25AA6E54D511AD74009027B1110F5BAFEB@ORION>
On Fri, Jan 09, 2004 at 03:30:28PM -0500, Steven Blakeslee wrote:
> I am trying to download a specific revision of the linuxppc_2_4_devel tree,
> tag v2.4.21_linuxppc_2_4_devel, at
> http://ppc.bkbits.net:8080/linuxppc_2_4_devel
>
> The command I give is
> bk clone -r1.1308.1.36 http://ppc.bkbits.net/linuxppc_2_4_devel
>
> I thought the -r1.1308.1.36 would tell it to download up to changset
> 1.1308.1.36 but I keep getting the most recent version. Can you please tell
> me what I am doing wrong.
bk clone / pull just manages a copy of the repository. You need to
export a specific version of the tree. After the bk clone command, try
this:
bk export -rv2.4.21_linuxppc_2_4_devel targetdir
--
There are 10 types of people in the world: Those who understand binary, and those who don't.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-01-12 1:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 20:30 downloading source with specific changeset Steven Blakeslee
2004-01-12 1:16 ` Wouter Cloetens [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=20040112011642.GI9059@roadkill.intern.mind.be \
--to=wouter@mind.be \
--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).