bzr.dev rsync copy is broken?

[Erik Bågfors]

2006/3/28, Matthieu Moy <Matthieu.Moy at imag.fr>:
> William Dode <wilk-ml at flibuste.net> writes:
>
> >> What about a different command than pull to update a working tree ?
> >
> > i wanted to say instead of push...
> >
> >>
> >> bzr export sftp:... | ftp:... | rsync:...
>
> Indeed, a simpler semantics would be:
>
> If there is a working tree, update it.
> Otherwise, don't update it

I think the problem is that it's very expensive to update the working
tree on a none local location.  Each file has to be read to verify
that it hasn't been updated in the tree, if it has a merge has to be
done that merges the changes that are being pushed, with the changes
that's done in the working tree.

I don't think it's doable over sftp.  There could however be a
--overwrite-tree flag to puch that will unconditionally overwrite it?

I think a smart server will solve this.

/Erik