Re: cset transfer script

On Tue, Feb 28, 2006 at 04:23:38PM -0500, Tristan Van Berkom wrote:
> Hey hey,
>     still on the hunt for my temporary binpool repo solution...
> I came across this script (that I'll attach to this mail...) that
> generates a patch from a repo via bk export and then applies it
> to another via bk import
> (I know 'bk pull -r <changeset number> <repository>'
> was already a prototyped feature request... basicly this script
> is a hack to fulfill that need).
> 
> I'm hoping I can do something similar; to stack on one changeset
> at a time from one repo to the other repo without doing it all
> in one 'bk pull' pass (which will result in OOM condition);

What is the graph structure of the csets that need to be moved?
Is it a straight line or include branch and merges?

You can move one at a time if it is a straight line history
by using something like

  for each change
    # in local side
    bk send -r<rev> - > somechange
    # in remote side
    bk receive -a < somechange

If you have branch and merge, then it won't work to move one change
at a time.

> Hmmm, is 'bk pull' essentially a script that calls the underlying
> scripts ? (maybe I can examine that script to write my own... where
> would I find that script ?).

No, it is not a script.

> Any clues as to how I can modify the attached script to work with
> binary files in changesets ?

I didn't see any attachment.  You can send it to me and I'll take
a look.

Rick