bzr.dev rsync copy is broken?
Matthieu Moy
Matthieu.Moy at imag.fr
Tue Mar 28 12:46:32 BST 2006
"Erik Bågfors" <zindar at gmail.com> writes:
>> 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.
Yes, but if it is too costly to update the tree, then why would you
want to have one anyway? And with my proposal, if you don't have a
tree, you don't pay the penality.
Maybe it can be interesting to have a --dont-update-tree flag for
people who explicitely want to run "bzr update" on the server.
> Each file has to be read to verify that it hasn't been updated in
> the tree,
This is not true. You can compare the inventories, and then take into
account only the files which have been modified by the push (which
you'll have to read and write back).
> I think a smart server will solve this.
Yes, it would do it much more efficiently. But it requires python &
bzr on the server.
--
Matthieu
More information about the bazaar
mailing list