Matt McCutchen's Web Site
/
rsync
/
rsync.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
ff57065
)
Fixed a typo and added a couple clarifying phrases to the exclude
author
Wayne Davison
<wayned@samba.org>
Tue, 22 Apr 2003 18:09:22 +0000
(18:09 +0000)
committer
Wayne Davison
<wayned@samba.org>
Tue, 22 Apr 2003 18:09:22 +0000
(18:09 +0000)
descriptions.
rsync.yo
patch
|
blob
|
blame
|
history
diff --git
a/rsync.yo
b/rsync.yo
index
5360d43
..
5f8623c
100644
(file)
--- a/
rsync.yo
+++ b/
rsync.yo
@@
-871,8
+871,8
@@
skipped. If it is an include pattern then that filename is not
skipped. If no matching include/exclude pattern is found then the
filename is not skipped.
skipped. If no matching include/exclude pattern is found then the
filename is not skipped.
-The filenames matched against the exclude/incl
du
e patterns are
-relative to the base directories so patterns should not
+The filenames matched against the exclude/incl
ud
e patterns are
+relative to the base directories
,
so patterns should not
include the path elements to those base directories. The
only way in which a pattern will match the absolute path of
a file or directory is if the base path is the root directory.
include the path elements to those base directories. The
only way in which a pattern will match the absolute path of
a file or directory is if the base path is the root directory.
@@
-893,7
+893,8
@@
itemize(
start of the filename, otherwise it is matched against the end of
the filename.
This is the equivalent of a leading ^ in regular expressions.
start of the filename, otherwise it is matched against the end of
the filename.
This is the equivalent of a leading ^ in regular expressions.
- Thus "/foo" would match a file called "foo" at the base of the tree.
+ Thus "/foo" would match a file called "foo" at the base of the
+ transferred tree.
On the other hand, "foo" would match any file called "foo"
anywhere in the tree because the algorithm is applied recursively from
top down; it behaves as if each path component gets a turn at being the
On the other hand, "foo" would match any file called "foo"
anywhere in the tree because the algorithm is applied recursively from
top down; it behaves as if each path component gets a turn at being the
@@
-929,8
+930,9
@@
itemize(
include/exclude list is reset, removing all previously defined patterns.
)
include/exclude list is reset, removing all previously defined patterns.
)
-The +/- rules are most useful in exclude lists, allowing you to have a
-single exclude list that contains both include and exclude options.
+The +/- rules are most useful in a list that was read from a file, allowing
+you to have a single exclude list that contains both include and exclude
+options.
If you end an exclude list with --exclude '*', note that since the
algorithm is applied recursively that unless you explicitly include
If you end an exclude list with --exclude '*', note that since the
algorithm is applied recursively that unless you explicitly include