summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-04-14 15:52:46 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-04-14 15:52:46 -0400
commitc1cffccf3de31c80ccfcf6e28844a0339847b201 (patch)
tree2fd233eca59ec51c9edb531508c3c2c797b333f1
parent4c3d5e2b8587c74cc1d07d7ba24570a4ef25efca (diff)
comment
-rw-r--r--doc/forum/files_vanishing/comment_1_eb69e88aee0005fca74dd540293e57ca._comment14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/forum/files_vanishing/comment_1_eb69e88aee0005fca74dd540293e57ca._comment b/doc/forum/files_vanishing/comment_1_eb69e88aee0005fca74dd540293e57ca._comment
new file mode 100644
index 000000000..8282b9e38
--- /dev/null
+++ b/doc/forum/files_vanishing/comment_1_eb69e88aee0005fca74dd540293e57ca._comment
@@ -0,0 +1,14 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2016-04-14T19:50:52Z"
+ content="""
+Suggest you run git log --stat to see if you can find a commit that deleted
+the missing files. Reverting the commit should then get the files back.
+
+There have been several bugs of this kind in direct mode. Using such an old
+git-annex from 2014 makes it more likely you'll hit an old bug like this.
+
+The new v6 repository mode should be much less likely to have this kind of
+bug.
+"""]]