From d72d76c06fad84cc271afa09a6bdc393c2ccdc93 Mon Sep 17 00:00:00 2001 From: Franky Date: Wed, 17 Jun 2020 19:01:44 +0000 Subject: [PATCH] --- .../Running_fsck_on_a_remote_completely_drops_the_file.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn b/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn index 9935528678..1bf9265947 100644 --- a/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn +++ b/doc/bugs/Running_fsck_on_a_remote_completely_drops_the_file.mdwn @@ -8,7 +8,7 @@ Running fsck on a remote completely drops the file * Run `git-annex fsck` * git-annex will notice the corruption and completely drop the file from the remote -I expect git-annex to never drop data unless specified as also mentioned in https://git-annex.branchable.com/walkthrough/fsck__58___when_things_go_wrong/ +I expect git-annex to never drop data unless specified as also mentioned [here](https://git-annex.branchable.com/walkthrough/fsck__58___when_things_go_wrong) I would rather look at the corrupted file myself and figure out the best course of action instead of losing it completely.