moreinfo

1 files changed, 23 insertions, 0 deletions

diff --git a/doc/bugs/Export_fails_for_files_directly_in_git_repo/comment_1_0077e5e36896116059070e26143f03d0._comment b/doc/bugs/Export_fails_for_files_directly_in_git_repo/comment_1_0077e5e36896116059070e26143f03d0._comment
new file mode 100644
index 000000000..a2015a49e
--- /dev/null
+++ b/doc/bugs/Export_fails_for_files_directly_in_git_repo/comment_1_0077e5e36896116059070e26143f03d0._comment
@@ -0,0 +1,23 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2017-10-30T16:11:42Z"
+ content="""
+More information needed to reproduce this.
+
+Normally adding a "file.txt" would not ever result in its key
+containing a space like that. So, it seems to me you must have
+already added a file with the same content to the annex, in a
+way that caused its key's name to contain a space. 
+
+(I guess you're also using v6 mode, that's the only way "git add" would
+add the file to git-annex.)
+
+Also note that the limitation on spaces in key names only impacts
+exporting to external special remotes, so "exp" must be some kind
+of external special remote. (I was not aware of any that
+supported exports yet..)
+
+Suggest you `git show a05faa1` and see what key it used, that will
+make the above speculations a bit more concrete.
+"""]]