summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-07-07 13:31:13 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-07-07 13:31:13 -0400
commit232c7d2f21dc522ae9e859244c55863070c74bed (patch)
tree01939616f71e09f432e47c9a24b34a211bb51395
parentcb18e044c7b6062488306092e17dffacdd3e1989 (diff)
confirm
-rw-r--r--doc/bugs/direct_mode_should_refuse_to_merge_with_illegal_filenames.mdwn5
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/bugs/direct_mode_should_refuse_to_merge_with_illegal_filenames.mdwn b/doc/bugs/direct_mode_should_refuse_to_merge_with_illegal_filenames.mdwn
index d8377be0d..102404be4 100644
--- a/doc/bugs/direct_mode_should_refuse_to_merge_with_illegal_filenames.mdwn
+++ b/doc/bugs/direct_mode_should_refuse_to_merge_with_illegal_filenames.mdwn
@@ -32,4 +32,7 @@ So, how to detect when `git merge` has skipped creating illegal filenames?
----
-Alternatively, git-annex could learn/probe the full set of characters not allowed in filenames, and examine merges before performing them, and refuse to do anything if the merge added an illegal filename.
+Alternatively, git-annex could learn/probe the full set of characters not allowed in filenames, and examine merges before performing them, and refuse to do anything if the merge added an illegal filename.a
+
+[[!tag confirmed]]
+