Added a comment
authorjohannes@12f1850a57e13cc234b5ebf88a5d3ac68915a6c2 <johannes@web>
Wed, 19 Oct 2016 10:28:13 +0000 (10:28 +0000)
committeradmin <admin@branchable.com>
Wed, 19 Oct 2016 10:28:13 +0000 (10:28 +0000)
doc/bugs/assistant_crashes_in_TransferScanner/comment_1_e626d6fc90a4af8906973121149eef7d._comment [new file with mode: 0644]

diff --git a/doc/bugs/assistant_crashes_in_TransferScanner/comment_1_e626d6fc90a4af8906973121149eef7d._comment b/doc/bugs/assistant_crashes_in_TransferScanner/comment_1_e626d6fc90a4af8906973121149eef7d._comment
new file mode 100644 (file)
index 0000000..514c85a
--- /dev/null
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="johannes@12f1850a57e13cc234b5ebf88a5d3ac68915a6c2"
+ nickname="johannes"
+ avatar="http://cdn.libravatar.org/avatar/7acaf4a71b0b93cc419195f58f4cd54c"
+ subject="comment 1"
+ date="2016-10-19T10:28:13Z"
+ content="""
+I just noticed that I get the same error when executing `git annex sync --content`. Nevertheless, the following commands are running flawlessly:
+
+* `git annex sync`
+* `git annex get --auto`
+* `git annex copy -t origin --auto`.
+"""]]