From 232c7d2f21dc522ae9e859244c55863070c74bed Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 7 Jul 2014 13:31:13 -0400 Subject: confirm --- .../direct_mode_should_refuse_to_merge_with_illegal_filenames.mdwn | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) 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]] + -- cgit v1.2.3