[SCM] The rsync repository. - branch master updated

Rsync CVS commit messages rsync-cvs at lists.samba.org
Wed Aug 24 04:13:06 UTC 2022

The branch, master has been updated
       via  034d5e87 Tweak a couple links.
      from  ad891743 Mention that copying to a case-ignoring filesystem can be problematical.


- Log -----------------------------------------------------------------
commit 034d5e877040358f5d341771a6cca5f5dc086300
Author: Wayne Davison <wayne at opencoder.net>
Date:   Tue Aug 23 21:05:54 2022 -0700

    Tweak a couple links.


Summary of changes:
 rsync.1.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Changeset truncated at 500 lines:

diff --git a/rsync.1.md b/rsync.1.md
index dfdd7df3..4d0b8eca 100644
--- a/rsync.1.md
+++ b/rsync.1.md
@@ -198,13 +198,13 @@ See the [`--trust-sender`](#opt) option for additional details.
 CAUTION: it is not particularly safe to use rsync to copy files from a
 case-preserving filesystem to a case-ignoring filesystem.  If you must perform
 such a copy, you should either disable symlinks via `--no-links` or enable the
-munging of symlinks via [`--munge-links`](#opt)) (and make sure you use the
+munging of symlinks via [`--munge-links`](#opt) (and make sure you use the
 right local or remote option).  This will prevent rsync from doing potentially
 dangerous things if a symlink name overlaps with a file or directory. It does
 not, however, ensure that you get a full copy of all the files (since that may
 not be possible when the names overlap). A potentially better solution is to
 list all the source files and create a safe list of filenames that you pass to
-the [`--files-from`)(#opt) option.  Any files that conflict in name would need
+the [`--files-from`](#opt) option.  Any files that conflict in name would need
 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

The rsync repository.

More information about the rsync-cvs mailing list