Large changeset & binpool [ was Killing bk repo ]

Ok,
    it seems that practically; for now the only problem I
have with this tarball repository is propagating the changesets;
when I run bk pull from another repo and there are large changesets;
I get "cannot allocate memory"...

is there a way using some obscure bitkeeper scripts to manually
apply the changesets one by one or something... maybe dropping
some expensive error checking or something that will allow me
to propagate the changesets ?

Maybe its easier to do considering that in the case of a merge...
you always just take the tarball that was the latest commit
(by timestamp or something) ?

Also (ahem) Larry mentioned something about a concept called
binpool in development... can I get any more information on
how that will work and when I can use it (cause I'm sure that
will solve our problems without rewriting alot of build
related scripts).

I guess its worth a shot to ask; can I be your guinea pig and
try out whatever you might have working along those lines ?

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?