From bc3f9999b0899afd0f5eac0421106e0045135e41 Mon Sep 17 00:00:00 2001
From: Franky <Franky@web>
Date: Wed, 17 Jun 2020 19:07:00 +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 1bf9265947..28d18bdd18 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
@@ -12,7 +12,7 @@ I expect git-annex to never drop data unless specified as also mentioned [here](
 
 I would rather look at the corrupted file myself and figure out the best course of action instead of losing it completely.
 
-At this point, I'm no longer running fsck on remotes.
+At this point, I'm working around it by not running fsck on remotes, since local fsck seems to work as expected.
 
 
 ### What version of git-annex are you using? On what operating system?