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
On Sat, 2009-02-28 at 13:31 +0100, Kurt wrote:
Hi - is there a clever way to identify files that have been change on
the local _and_ the remote location? Without such a check it may
happen, that changes are lost without even noticing.
One way to identify such files would be to do a
Hi - is there a clever way to identify files that have been change on
the local _and_ the remote location? Without such a check it may
happen, that changes are lost without even noticing.
One way to identify such files would be to do a dry-run upsync, then a
dry-run downsync, find files
