[Unison-hackers] File copying/moving optimizations

[Jerry Haltom]

Ahh. That isn't in the man page. Hadn't noticed it! THanks!

On Thu, 2005-11-03 at 09:16 +0100, Alan Schmitt wrote:
> On 2 nov. 05, at 23:03, Jerry Haltom wrote:
> 
> > So I notice that Unison completely re-downloads a file when it is the
> > result of a copy or a move. Makes sense from a simple implementation
> > point of view, but I was wondering about an alternative.
> >
> > When a file is seen as not existing in the replica, it makes sense  
> > to me
> > for the data of the file to be searched for in the replica, and copied
> > to the new name if found. The original says a file with a certain MD5
> > sum exists at a new location, the replicate searches for an existing
> > file with that MD5 sum and copies it.
> >
> > Seems like this could speed up synchronization in some specific  
> > cases by
> > a good deal. Simply renaming a large top level directory would  
> > result in
> > a new directory being created in the replica and populated from the
> > previous data. Much faster!
> >
> > Thoughts?
> 
> Well, it should already be the case. According to the manual:
> 
> xferbycopying
> When this preference is set, Unison will try to avoid transferring  
> file contents across the network by recognizing when a file with the  
> required contents already exists in the target replica. This usually  
> allows file moves to be propagated very quickly. The default value is  
> true.
> 
> Alan Schmitt
> 
> _______________________________________________
> Unison-hackers mailing list
> Unison-hackers at lists.seas.upenn.edu
> http://lists.seas.upenn.edu/mailman/listinfo/unison-hackers
-- 
Jerry Haltom <wasabi at larvalstage.net>