Treat files that were modified locally and remote

[Wayne Davison]

On Sat, Feb 28, 2009 at 01:31:32PM +0100, Kurt wrote:
> One way to identify such files would be to do a dry-run upsync, then a 
> dry-run downsync, find files that would have been sync'ed in both dry-runs, 
> and then prompt the user for some action.

Assuming that you mean to use the -u option, that still wouldn't work
very well because you don't know if the updated file is newer than the
original file, or a newer change than the also-changed file on the other
side.  You need something with a DB, such as unison, or (perhaps) the
drsync perl wrapper script.

..wayne..