Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
L
liblongpath-rsync
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
liblongpath
liblongpath-rsync
Commits
c5b6e57a
Commit
c5b6e57a
authored
Jan 20, 2007
by
Wayne Davison
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fixed some typos Matt found.
parent
ca947dea
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
rsync.yo
rsync.yo
+4
-4
No files found.
rsync.yo
View file @
c5b6e57a
...
@@ -464,7 +464,7 @@ by the client at the start of a daemon transfer. This suppresses the
...
@@ -464,7 +464,7 @@ by the client at the start of a daemon transfer. This suppresses the
message-of-the-day (MOTD) text, but it also affects the list of modules
message-of-the-day (MOTD) text, but it also affects the list of modules
that the daemon sends in response to the "rsync host::" request (due to
that the daemon sends in response to the "rsync host::" request (due to
a limitation in the rsync protocol), so omit this option if you want to
a limitation in the rsync protocol), so omit this option if you want to
request the list of modules from the d
ea
mon.
request the list of modules from the d
ae
mon.
dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
dit(bf(-I, --ignore-times)) Normally rsync will skip any files that are
already the same size and have the same modification time-stamp.
already the same size and have the same modification time-stamp.
...
@@ -941,7 +941,7 @@ combined with the bf(--ignore-existing) option, no files will be updated
...
@@ -941,7 +941,7 @@ combined with the bf(--ignore-existing) option, no files will be updated
dit(bf(--ignore-existing)) This tells rsync to skip updating files that
dit(bf(--ignore-existing)) This tells rsync to skip updating files that
already exist on the destination (this does em(not) ignore existing
already exist on the destination (this does em(not) ignore existing
directores, or nothing would get done). See also bf(--existing).
director
i
es, or nothing would get done). See also bf(--existing).
dit(bf(--remove-source-files)) This tells rsync to remove from the sending
dit(bf(--remove-source-files)) This tells rsync to remove from the sending
side the files (meaning non-directories) that are a part of the transfer
side the files (meaning non-directories) that are a part of the transfer
...
@@ -1113,7 +1113,7 @@ communicate.
...
@@ -1113,7 +1113,7 @@ communicate.
One tricky example is to set a different default directory on the remote
One tricky example is to set a different default directory on the remote
machine for use with the bf(--relative) option. For instance:
machine for use with the bf(--relative) option. For instance:
quote(tt( rsync -avR --rsync-path="cd /a/b && rsync" hst:c/d /e/))
quote(tt( rsync -avR --rsync-path="cd /a/b && rsync" h
o
st:c/d /e/))
dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
dit(bf(-C, --cvs-exclude)) This is a useful shorthand for excluding a
broad range of files that you often don't want to transfer between
broad range of files that you often don't want to transfer between
...
@@ -1655,7 +1655,7 @@ each file's destination directory, but if you've specified the
...
@@ -1655,7 +1655,7 @@ each file's destination directory, but if you've specified the
bf(--partial-dir) option, that directory will be used instead. See the
bf(--partial-dir) option, that directory will be used instead. See the
comments in the bf(--partial-dir) section for a discussion of how this
comments in the bf(--partial-dir) section for a discussion of how this
".~tmp~" dir will be excluded from the transfer, and what you can do if
".~tmp~" dir will be excluded from the transfer, and what you can do if
you w
na
t rsync to cleanup old ".~tmp~" dirs that might be lying around.
you w
an
t rsync to cleanup old ".~tmp~" dirs that might be lying around.
Conflicts with bf(--inplace) and bf(--append).
Conflicts with bf(--inplace) and bf(--append).
This option uses more memory on the receiving side (one bit per file
This option uses more memory on the receiving side (one bit per file
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment