[SCM] The rsync repository. - branch master updated

[Rsync CVS commit messages]

The branch, master has been updated
       via  9799c75b Improve `--mkpath` a bit more.
      from  ad6245f3 Include "buildall" flag in the release commit.

https://git.samba.org/?p=rsync.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit 9799c75b2463c725f1829b8e1b817f122af47835
Author: Wayne Davison <wayne at opencoder.net>
Date:   Sun Oct 16 12:23:39 2022 -0700

    Improve `--mkpath` a bit more.

-----------------------------------------------------------------------

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


Changeset truncated at 500 lines:

diff --git a/rsync.1.md b/rsync.1.md
index 65cf8815..6cd783eb 100644
--- a/rsync.1.md
+++ b/rsync.1.md
@@ -1150,22 +1150,22 @@ expand it.
 0.  `--mkpath`
 
     Create a missing path component of the destination path. By default, rsync
-    allows only the final element of the destination path to not exist, which
+    allows only the final component of the destination path to not exist, which
     is an attempt to help you to validate your destination path.  With this
-    option, rsync creates all the missing destination-path components just as
-    if `mkdir -p $DEST_PATH` had been run.
+    option, rsync creates all the missing destination-path components, just as
+    if `mkdir -p $DEST_PATH` had been run on the receiving side.
 
     When specifying a destination path, including a trailing slash ensures that
-    rsync always treats the whole path as the directory name to be created,
-    even if the source arg is a single filename. See the [COPYING TO A
-    DIFFERENT NAME](#) section for full details on how rsync decides if a final
-    destination path element is a directory element or not.
+    the whole path is treated as directory names to be created, even when the
+    file list has a single item. See the [COPYING TO A DIFFERENT NAME](#)
+    section for full details on how rsync decides if a final destination-path
+    component should be created as a directory or not.
 
     If you would like the newly-created destination dirs to match the dirs on
     the sending side, you should be using [`--relative`](#opt) (`-R`) instead
     of `--mkpath`.  For instance, the following two commands result in the same
-    destination tree, but it is only the second command that ensures that the
-    "some/extra/path" elements match the dirs on the sending side:
+    destination tree, but only the second command ensures that the
+    "some/extra/path" components match the dirs on the sending side:
 
     >     rsync -ai --mkpath host:some/extra/path/*.c some/extra/path/
     >     rsync -aiR host:some/extra/path/*.c ./


-- 
The rsync repository.