diff options
author | 2011-11-08 12:23:03 -0400 | |
---|---|---|
committer | 2011-11-08 12:23:03 -0400 | |
commit | 67c9f84a1f80a0b8335a1e6edce2cd143d71b4c9 (patch) | |
tree | bd5d91cc2e4d4107fa65b9bb6d5fbc8def191cad /doc/walkthrough/unused_data.mdwn | |
parent | d35cd6ff262bc7013e5bb8fe63e8251c0e4ba8b3 (diff) |
fix broken links
Diffstat (limited to 'doc/walkthrough/unused_data.mdwn')
-rw-r--r-- | doc/walkthrough/unused_data.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/walkthrough/unused_data.mdwn b/doc/walkthrough/unused_data.mdwn index bd6c39871..518550ac0 100644 --- a/doc/walkthrough/unused_data.mdwn +++ b/doc/walkthrough/unused_data.mdwn @@ -2,7 +2,7 @@ It's possible for data to accumulate in the annex that no files in any branch point to anymore. One way it can happen is if you `git rm` a file without first calling `git annex drop`. And, when you modify an annexed file, the old content of the file remains in the annex. Another way is when -migrating between key-value [[backends|backend]]. +migrating between key-value [[backends]]. This might be historical data you want to preserve, so git-annex defaults to preserving it. So from time to time, you may want to check for such data and |