|
@@ -334,8 +334,8 @@ borg usually just stores their metadata:
|
|
|
Other flags used include:
|
|
|
|
|
|
- 'i' = backup data was read from standard input (stdin)
|
|
|
-- '-' = dry run, item was *not* backed up
|
|
|
-- 'x' = excluded, item was *not* backed up
|
|
|
+- '-' = item would be included in archive(s) (if not in dry-run mode)
|
|
|
+- 'x' = item was excluded - or would be excluded from archive(s) (if not in dry-run mode)
|
|
|
- '?' = missing status code (if you see this, please file a bug report!)
|
|
|
|
|
|
Reading backup data from stdin
|
|
@@ -384,4 +384,4 @@ to borg (maybe implementing your own recursion or your own rules), you can use
|
|
|
fail to create an archive should the command fail).
|
|
|
|
|
|
Borg supports paths with the slashdot hack to strip path prefixes here also.
|
|
|
-So, be careful not to unintentionally trigger that.
|
|
|
+So, be careful not to unintentionally trigger that.
|