docs: bisync: clarification of --resync

This commit is contained in:
Gerard Bosch 2023-02-28 12:47:28 +01:00 committed by GitHub
parent 5039f9be48
commit dd72aff98a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -146,9 +146,9 @@ The base directories on the both Path1 and Path2 filesystems must exist
or bisync will fail. This is required for safety - that bisync can verify or bisync will fail. This is required for safety - that bisync can verify
that both paths are valid. that both paths are valid.
When using `--resync` a newer version of a file on the Path2 filesystem When using `--resync`, a newer version of a file either on Path1 or Path2
will be overwritten by the Path1 filesystem version. filesystem, will overwrite the file on the other path (only the last version
Carefully evaluate deltas using [--dry-run](/flags/#non-backend-flags). will be kept). Carefully evaluate deltas using [--dry-run](/flags/#non-backend-flags).
For a resync run, one of the paths may be empty (no files in the path tree). For a resync run, one of the paths may be empty (no files in the path tree).
The resync run should result in files on both paths, else a normal non-resync The resync run should result in files on both paths, else a normal non-resync