Re: Killing bitkeeper history

Mike Marty wrote:
> We use BitKeeper to manage some binaries in a separate repository from 
> our codebase.  To eliminate redundant disk space usage on our shared 
> volumes and to make read-only "checkouts" fast for day-to-day usage, we 
> just do a "bk export" instead of a "bk clone" for normal work.  We 
> rarely  make changes to the binaries so this works fine.

It definitly sounds like I want to do that... well I definitly
want to do that for the automated build process that clones
all the repos and builds (I'm assuming an export will cut down
build time significantly).... one problem... how can I do a:
     bk export bk://server:9901/INTEGRATION_REPOSITORY

export only seems to want to work on your local repository
(which is already cloned, *doh*)

Cheers,
                     -Tristan

-- 
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on usenet and in e-mail?