summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Lykos153 <Lykos153@web>2017-10-29 17:57:50 +0000
committerGravatar admin <admin@branchable.com>2017-10-29 17:57:50 +0000
commite8d1bb6ef80c3e08ba09af39d8e92454c1246472 (patch)
tree8ec0165be07e7d27b05decc68d4999a2227d9322
parent34f3d1235f00e1865bb4113d0b980f2df8f010b0 (diff)
-rw-r--r--doc/bugs/Export_fails_for_files_directly_in_git_repo.mdwn31
1 files changed, 31 insertions, 0 deletions
diff --git a/doc/bugs/Export_fails_for_files_directly_in_git_repo.mdwn b/doc/bugs/Export_fails_for_files_directly_in_git_repo.mdwn
new file mode 100644
index 000000000..439356d98
--- /dev/null
+++ b/doc/bugs/Export_fails_for_files_directly_in_git_repo.mdwn
@@ -0,0 +1,31 @@
+### Please describe the problem.
+I'm playing around with the new export function and it's working really fine so far. But just now I ran into problems when `git add`ing a file, see below.
+
+### What steps will reproduce the problem?
+
+[[!format sh """
+
+$ echo test > file.txt
+$ git add file.txt
+$ git annex sync
+commit
+[master a05faa1] git-annex in lykos@**:/tmp/testrepo2
+ 1 file changed, 1 insertion(+)
+ create mode 100644 file.txt
+ok
+$ git annex export --tracking master --to exp
+export exp file.txt
+git-annex: Sorry, this file cannot be stored on an external special remote because its key's name contains a space. To avoid this problem, you can run: git-annex migrate --backend=SHA1 and pass it the name of the file
+failed
+(recording state in git...)
+git-annex: export: 1 failed
+
+"""]]
+
+
+### What version of git-annex are you using? On what operating system?
+6.20171026-g43d011a52 on Arch Linux
+
+### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
+Of course ;) All the time
+