aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2017-06-09 13:31:34 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2017-06-09 13:31:34 -0400
commit2ccbd580091d3fb1a4abbde6f1de1670988bf9eb (patch)
treeeaa913ee602e2e31d9550960364b409021445706
parent2e484a48d306f48849ba08c7945cb6d2a70a6185 (diff)
followup
-rw-r--r--doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment b/doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment
new file mode 100644
index 000000000..34ed9f1d7
--- /dev/null
+++ b/doc/bugs/sync_claims_data_loss_but_seems_to_just_lose_tracking/comment_2_f686273c6be899d2a8bbaabd03a47fbf._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 2"""
+ date="2017-06-09T17:25:23Z"
+ content="""
+I have not had any luck with reproducing the problem, using
+your script, on Debian unstable. The transfer repo gets
+the file contents and both it and the source repo knows where they are.
+
+Do you see the same behavior if, rather than running the assistant
+for 30 seconds, you run `git annex sync --content` ?
+
+Are you using git-annex in direct mode and/or on an unusual filesystem?
+"""]]