Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#6231: Clarify where paths are relative to #7737

Open
wants to merge 10 commits into
base: master
Choose a base branch
from
10 changes: 5 additions & 5 deletions docs/usage/help.rst.inc
Original file line number Diff line number Diff line change
Expand Up @@ -18,13 +18,13 @@ unwanted ones. Patterns can be used
- for ``PATH`` arguments that explicitly support them.

Borg always stores all file paths normalized and relative to the
current recursion root. The recursion root is also named ``PATH`` in
Borg commands like `borg create` that do a file discovery, so do not
confuse the root with the ``PATH`` argument of e.g. `borg extract`.
first directory of the current recursion root. The recursion root is also named
``PATH`` in Borg commands like `borg create` that do a file discovery, so do
not confuse the root with the ``PATH`` argument of e.g. `borg extract`.
jefft marked this conversation as resolved.
Show resolved Hide resolved
jefft marked this conversation as resolved.
Show resolved Hide resolved

Starting with Borg 1.2, paths that are matched against patterns always
appear relative. If you give ``/absolute/`` as root, the paths going
into the matcher will start with ``absolute/``.
appear relative. If you give ``/opt/app/`` as root, the paths going
into the matcher will start with ``opt/``.
jefft marked this conversation as resolved.
Show resolved Hide resolved
If you give ``../../relative`` as root, the paths will be normalized
as ``relative/``.

Expand Down