From 66e92636d27ce672a5f0221aac336f892a82630c Mon Sep 17 00:00:00 2001
From: goebbe <35854226+goebbe@users.noreply.github.com>
Date: Sun, 24 Nov 2024 13:44:39 +0100
Subject: [PATCH] Clarify  excluded and included flags for dry-run in borg the
 docs

Rewording of the "flags" description in the docs of borg 1.4.
https://github.com/borgbackup/borg/issues/8556
---
 docs/usage/create.rst.inc | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/usage/create.rst.inc b/docs/usage/create.rst.inc
index d27a2b083..b02b6003b 100644
--- a/docs/usage/create.rst.inc
+++ b/docs/usage/create.rst.inc
@@ -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.
\ No newline at end of file
+So, be careful not to unintentionally trigger that.