From: Wayne Davison Date: Mon, 1 May 2023 00:28:50 +0000 (-0700) Subject: A couple spelling tweaks; tweak order. X-Git-Tag: v3.3.0~11 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=86f41650fb048fa5857a137f70074d77ebe06e36;p=thirdparty%2Frsync.git A couple spelling tweaks; tweak order. --- diff --git a/NEWS.md b/NEWS.md index 1d3a158b1..67869cccb 100644 --- a/NEWS.md +++ b/NEWS.md @@ -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 diff --git a/rsync.1.md b/rsync.1.md index 16dbf20c2..894b36632 100644 --- a/rsync.1.md +++ b/rsync.1.md @@ -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.