summaryrefslogtreecommitdiff
path: root/doc/walkthrough/recover_data_from_lost+found.mdwn
diff options
context:
space:
mode:
authorGravatar https://www.google.com/accounts/o8/id?id=AItOawl9sYlePmv1xK-VvjBdN-5doOa_Xw-jH4U <Richard@web>2011-04-03 08:58:20 +0000
committerGravatar admin <admin@branchable.com>2011-04-03 08:58:20 +0000
commite8796f439d4d9d043c87479d1c2680d92c0d1fc8 (patch)
tree7157ea6eab9498de25219536e93466d27f7d7289 /doc/walkthrough/recover_data_from_lost+found.mdwn
parent4881a1833a110137f1320643ac01b33af6ea5e4c (diff)
Diffstat (limited to 'doc/walkthrough/recover_data_from_lost+found.mdwn')
-rw-r--r--doc/walkthrough/recover_data_from_lost+found.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/walkthrough/recover_data_from_lost+found.mdwn b/doc/walkthrough/recover_data_from_lost+found.mdwn
index f101b3caf..48ef2a1d7 100644
--- a/doc/walkthrough/recover_data_from_lost+found.mdwn
+++ b/doc/walkthrough/recover_data_from_lost+found.mdwn
@@ -14,6 +14,6 @@ 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 SHA1 backend is used, but even
+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.