From 96ad9f53fe22dcc7d166d8ead166f4ddd9f3289c Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 4 Aug 2015 15:35:04 -0400 Subject: response --- .../comment_1_a98072047799a0c9ba8c5589471f6a7b._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/bugs/linux_standalone_git_annex_won__39__t_work_in_a_directory_whose_path_contains_:_or___59__/comment_1_a98072047799a0c9ba8c5589471f6a7b._comment diff --git a/doc/bugs/linux_standalone_git_annex_won__39__t_work_in_a_directory_whose_path_contains_:_or___59__/comment_1_a98072047799a0c9ba8c5589471f6a7b._comment b/doc/bugs/linux_standalone_git_annex_won__39__t_work_in_a_directory_whose_path_contains_:_or___59__/comment_1_a98072047799a0c9ba8c5589471f6a7b._comment new file mode 100644 index 000000000..ae88142b6 --- /dev/null +++ b/doc/bugs/linux_standalone_git_annex_won__39__t_work_in_a_directory_whose_path_contains_:_or___59__/comment_1_a98072047799a0c9ba8c5589471f6a7b._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2015-08-04T19:34:34Z" + content=""" +Nice analysis. + +I can't see any way to avoid this problem. So, seems like a "don't do that +then" situation. +"""]] -- cgit v1.2.3