Rsync 3.2.2 ransfer rate on my pet hardware is really poor, so every
improvement counts.
I noted that rsync writes a gmon file on the source path and leaves it there
when it terminates. When the source path is read-only, rsync complains that it
cannot write in it. For optimal use of the input
I have released rsync 3.2.3. It contains a smattering of bug fixes and
various enhancements.
To see a summary of all the recent changes, visit this link:
https://rsync.samba.org/ftp/rsync/NEWS#3.2.3
You can download the source tar file and its signature from here:
I have released rsync 3.2.3. It contains a smattering of bug fixes and
various enhancements.
To see a summary of all the recent changes, visit this link:
https://rsync.samba.org/ftp/rsync/NEWS#3.2.3
You can download the source tar file and its signature from here:
The branch, master has been updated
via e94bad1c Preparing for release of 3.2.3
via 617d726a Tweak a comment.
from 020eda88 Change fetch depth.
https://git.samba.org/?p=rsync.git;a=shortlog;h=master
- Log -
The annotated tag, v3.2.3 has been created
at 1a2d16c0bd161481cbf0acc06dceb1ce788f0d09 (tag)
tagging e94bad1c156fc3910f24e2b3b71a81b0b0bdeb70 (commit)
replaces v3.2.3pre1
tagged by Wayne Davison
on Thu Aug 6 20:58:52 2020 -0700
- Log
