mirror/rsync
1
0
Fork 0
mirror of https://github.com/RsyncProject/rsync.git synced 2026-05-14 01:45:45 -04:00
Code Issues Packages Projects Releases Wiki Activity

A couple spelling tweaks; tweak order.

Browse Source
This commit is contained in:
Wayne Davison
2023-04-30 17:28:50 -07:00
parent 9a06b2edb0
commit 86f41650fb
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
NEWS.md
View File

@@ -10,12 +10,12 @@
- Fixed an buffer overflow in the checksum2 code if SHA1 is being used for
the checksum2 algorithm.
- Fixed a string-comparison issue in the internal file-list code that affected
tr_TR.utf-8.
- Add a backtick to the list of characters that the filename quoting needs to
escape using backslashes.
- Fixed a string-comparison issue in the internal file-list code that affected
tr_TR.utf-8.
- Make sure that a local transfer marks the sender side as trusted.
- Change the argv handling to work with a newer popt library -- one that likes
@@ -100,7 +100,7 @@
- The `--fuzzy` option was optimized a bit to try to cut down on the amount of
computations when considering a big pool of files. The simple heuristic from
Kenneth Finnegan resuled in about a 2x speedup.
Kenneth Finnegan resulted in about a 2x speedup.
- If rsync is forced to use protocol 29 or before (perhaps due to talking to an
rsync before 3.0.0), the modify time of a file is limited to 4-bytes. Rsync

2
rsync.1.md
View File

@@ -245,7 +245,7 @@ to be copied to different destination directories using more than one copy.
While a copy of a case-ignoring filesystem to a case-ignoring filesystem can
work out fairly well, if no `--delete-during` or `--delete-before` option is
active, rsync can potentially update an existing file on the receiveing side
active, rsync can potentially update an existing file on the receiving side
without noticing that the upper-/lower-case of the filename should be changed
to match the sender.