summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2015-11-13 13:46:11 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2015-11-13 13:46:11 -0400
commitae6b2ead49181e846c38ab104b59ab6e9c529752 (patch)
tree85a0ca389e6b28cecb90139ef86a665fb8852176
parentd699ad231105204e3501d0b1c14eea6efb6f28c3 (diff)
update
-rw-r--r--doc/tips/recover_data_from_lost+found.mdwn5
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/tips/recover_data_from_lost+found.mdwn b/doc/tips/recover_data_from_lost+found.mdwn
index ceb43e3f3..0e7391a7f 100644
--- a/doc/tips/recover_data_from_lost+found.mdwn
+++ b/doc/tips/recover_data_from_lost+found.mdwn
@@ -14,6 +14,5 @@ First, check out the git repository again. Then, in the new checkout:
The way that works is that when git-annex adds the same content that was in
the repository before, all the old links to that content start working
-again. This works particularly well if the SHA* backends are used, but even
-with the default backend it will work pretty well, as long as fsck
-preserved the modification time of the files.
+again. So, this works as long as you're using one of the SHA* or other
+checksumming backends, which is the default.