From: Andy Isaacson <adi@hexapodia.org>
To: carbonated beverage <ramune@net-ronin.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: bk pull from bkbits screwy?
Date: Sat, 10 Jul 2004 17:15:29 -0500 [thread overview]
Message-ID: <20040710221529.GA12455@hexapodia.org> (raw)
In-Reply-To: <20040710065802.GA29604@net-ronin.org>
On Fri, Jul 09, 2004 at 11:58:02PM -0700, carbonated beverage wrote:
> I sent a patch a while ago to change the bk:// to http:// in the docs,
> but was told bk:// was working again. Just did a bk pull again right now,
> and bk:// doesn't seem to be working, whereas reparenting my repo to http://
> and doing a bk pull works. Am I missing something?
How about giving the command that didn't work, and the error messages it
printed? I just did a pull using bk://linux.bkbits.net/linux-2.5 and it
succeeded:
...
takepatch: 25577 new revisions, 0 conflicts in 6840 files
8439936 bytes uncompressed to 36145013, 4.28X expansion
Running resolve to apply new work ...
Using :0.0 as graphical display
resolve: found 491 renames in pass 1
resolve: resolved 491 renames in pass 2
resolve: applied 6840 files in pass 4
resolve: running consistency check, please wait...
100% |=================================================================| OK
Consistency check passed, resolve complete.
straum% bk pull
Pull bk://linux.bkbits.net/linux-2.5
-> file://data/linux/linux-2.5
Nothing to pull.
straum%
There are two different URL syntaxes that start "bk://" and perhaps
you're using the wrong one. (I got caught by that one a while back.)
And yes, bk:// is preferred over http://, in general.
-andy
next prev parent reply other threads:[~2004-07-10 22:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-10 6:58 bk pull from bkbits screwy? carbonated beverage
2004-07-10 22:15 ` Andy Isaacson [this message]
2004-07-11 16:05 ` carbonated beverage
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=20040710221529.GA12455@hexapodia.org \
--to=adi@hexapodia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ramune@net-ronin.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