diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-10-05 16:29:32 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-10-05 16:53:09 -0400 |
| commit | 4bb1630d88babbca7ad6581f68d4161c77280f2f (patch) | |
| tree | 277ba7ce982b8b888e0899ca6afee56cdea16f20 /doc/future_proofing.mdwn | |
| parent | aa38d92afcc0efbe7bb9786d00c45f71af756b75 (diff) | |
Support using v3 repositories without upgrading them to v5.
An easy change now that supportedVersions is a list. Since v3 and v5 are
identical other than version number, just add v3 to the list.
This commit was sponsored by andrea rota.
Diffstat (limited to 'doc/future_proofing.mdwn')
| -rw-r--r-- | doc/future_proofing.mdwn | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/future_proofing.mdwn b/doc/future_proofing.mdwn index e5bc89829..71a1b4a09 100644 --- a/doc/future_proofing.mdwn +++ b/doc/future_proofing.mdwn @@ -37,6 +37,14 @@ 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? + 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 + repository -- if modifying the original archived repository is not + desirable you can always make a copy of the repository and upgrade the + copy. + * What about encrypted special remotes? A [[fairly simple shell script using standard tools|Decrypting_files_in_special_remotes_without_git-annex]] (gpg and openssl) can decrypt files stored on such |