TapTap/FastSync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

docs: recount RSYNC_COMPAT to 141/0/4/0/0/2 after Phase 7 Waves B-D; refresh README short-option note
CI / lint (push) Successful in 1m42s
Details
CI / sanitizers (undefined) (push) Successful in 1m12s
Details
CI / sanitizers (address) (push) Successful in 1m14s
Details
CI / fuzz-build (push) Successful in 23s
Details
CI / coverage (push) Successful in 47s
Details
CI / valgrind (push) Successful in 39s
Details
CI / build-and-test (push) Successful in 4m44s
Details

Browse Source
This commit is contained in:
TapTap
2026-09-12 11:30:06 +02:00
parent 003a5e8f2f
commit f64d252faf
2 changed files with 9 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -2
View File
@@ -79,8 +79,10 @@ replacement for every rsync feature or protocol mode.
- `--dirs` is not implemented. Its compatibility aliases `--old-dirs` and
`--old-d` are recognized but rejected explicitly rather than silently using
FastSync's recursive directory behavior.
- Several rsync short options currently have FastSync-specific meanings. Do
not assume every short option is interchangeable yet.
- Short-option names are now rsync-parity (Phase 7 Wave A): FastSync's former
collisions were renamed (`-j`/`--threads`, `--preserve`, `--sendfile`,
`--chunk-serialization`, `--timeout`, `--ssh-port`), so `-m`, `-M`, `-f`,
`-s`, `-T`, `-p`, `-c`, `-a`, and `-z` follow rsync. See `RSYNC_COMPAT.md`.
The detailed flag matrix is maintained in
[`RSYNC_COMPAT.md`](RSYNC_COMPAT.md). It distinguishes implemented,