mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

mention synchronized upgrades limitation

Browse source
This commit is contained in:
anarcat 2018-12-04 21:07:11 +00:00 • committed by admin
parent 14e6d7cf2d
commit b4329466c3
1 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/upgrades.mdwn
View file

@ -44,6 +44,10 @@ The upgrade process needs to write to the repository. If the original
repository cannot be written to (due to eg being on readonly media), repository cannot be written to (due to eg being on readonly media),
the upgrade would need to be run in a copy of the repository. the upgrade would need to be run in a copy of the repository.
Some upgrades (most notably v6 and v7) require that all users of the
repository upgrade simultaneously, otherwise files may become unreadable
or unfetchable.
The upgrade events, so far: The upgrade events, so far:
## v6 -> v7 (git-annex version 7.x) ## v6 -> v7 (git-annex version 7.x)
@ -79,6 +83,10 @@ The behavior of some commands changes in an upgraded repository:
* `git annex unlock` and `git annex lock` change how the pointer to * `git annex unlock` and `git annex lock` change how the pointer to
the annexed content is stored in git. the annexed content is stored in git.
If you commit the unlocked files change, this will impact all clones of the
repository. This means all clones of the repository will need to run at least
v6 to correctly synchronise.
There is also a new `annex.thin` setting, which makes unlocked files in v6 There is also a new `annex.thin` setting, which makes unlocked files in v6
repositories be hard linked to their content, instead of a copy. This saves repositories be hard linked to their content, instead of a copy. This saves
disk space but means any modification of an unlocked file will lose the disk space but means any modification of an unlocked file will lose the