summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar openmedi <openmedi@web>2017-02-18 13:42:45 +0000
committerGravatar admin <admin@branchable.com>2017-02-18 13:42:45 +0000
commit447e52031b268282715d8e95c961378345114937 (patch)
tree955b968ff90d4ea2ab5f16a02368c386d06e74eb
parentcf0367e073974b87526d517f6731ffa4e2e12ff9 (diff)
-rw-r--r--doc/forum/git_annex_repairs_since_thursday.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/git_annex_repairs_since_thursday.mdwn b/doc/forum/git_annex_repairs_since_thursday.mdwn
index e0ce951e2..c1763b1f9 100644
--- a/doc/forum/git_annex_repairs_since_thursday.mdwn
+++ b/doc/forum/git_annex_repairs_since_thursday.mdwn
@@ -1,4 +1,4 @@
-I have not tried to get git annex to work in a bit. My troubles of recovering this annex repo have been documented here, here and here. On Thurs day I thought I give it another try. Since Thursday it tries to repair two out of three repos: my local repo on my laptop and my repo on an external harddrive I have. The b2 special remote repo appears to be fine, or not checked, I'm not sure.
+I have not tried to get git annex to work in a bit. My troubles of recovering this annex repo have been documented [here](http://git-annex.branchable.com/forum/git_annex_wants_to_repair_every_time_it__39__s_running/), [here](http://git-annex.branchable.com/forum/how_to_disaster_recovery/) and [here](http://git-annex.branchable.com/forum/__34__git_annex_assistant_--stop__34___doesn__39__t_work_in_OSX_10.11.4/). On Thurs day I thought I give it another try. Since Thursday it tries to repair two out of three repos: my local repo on my laptop and my repo on an external harddrive I have. The b2 special remote repo appears to be fine, or not checked, I'm not sure.
What can I do, to get it working again?