mirror of https://github.com/borgbackup/borg.git
Merge pull request #4318 from ThomasWaldmann/workaround-backslash-issue
work around the backslash issue, see #4280
This commit is contained in:
commit
38b40e805e
|
@ -2175,7 +2175,7 @@ class Archiver:
|
|||
any number of characters, '?' matching any single character, '[...]'
|
||||
matching any single character specified, including ranges, and '[!...]'
|
||||
matching any character not specified. For the purpose of these patterns,
|
||||
the path separator ('\\' for Windows and '/' on other systems) is not
|
||||
the path separator (backslash for Windows and '/' on other systems) is not
|
||||
treated specially. Wrap meta-characters in brackets for a literal
|
||||
match (i.e. `[?]` to match the literal character `?`). For a path
|
||||
to match a pattern, the full path must match, or it must match
|
||||
|
@ -2196,7 +2196,7 @@ class Archiver:
|
|||
shell patterns regular expressions are not required to match the full
|
||||
path and any substring match is sufficient. It is strongly recommended to
|
||||
anchor patterns to the start ('^'), to the end ('$') or both. Path
|
||||
separators ('\\' for Windows and '/' on other systems) in paths are
|
||||
separators (backslash for Windows and '/' on other systems) in paths are
|
||||
always normalized to a forward slash ('/') before applying a pattern. The
|
||||
regular expression syntax is described in the `Python documentation for
|
||||
the re module <https://docs.python.org/3/library/re.html>`_.
|
||||
|
|
Loading…
Reference in New Issue