diff options
| author |  elon.bing@6534c6b616a8fda498b5bfa4e48ca5a1ebb7c48e <elonbing@web> | 2017-11-02 20:39:05 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-11-02 20:39:05 +0000 |
| commit | 4965aded8c8bbc35e93917459f85e99f565c5af4 (patch) | |
| tree | 7793a905476d27593256101cb679e6c60f813f59 | |
| parent | c578186ff598a4d7b7b93d34e1fd5719e4f61ac3 (diff) | |
Fixed typo: "repisitory"
| -rw-r--r-- | doc/future_proofing.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/future_proofing.mdwn b/doc/future_proofing.mdwn index 71a1b4a09..a4d9ac24f 100644 --- a/doc/future_proofing.mdwn +++ b/doc/future_proofing.mdwn @@ -37,7 +37,7 @@ problem: another clone of the repository. Even if the filenames are lost, it's possible to [[tips/recover_data_from_lost+found]]. -* What about upgrades to the git-annex repisitory format? +* What about upgrades to the git-annex repository format? git-annex supports [[upgrades]] from all previous repository versions, and will always support upgrading from all of them to any new versions. Note that the upgrade process needs to modify the content of the |