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

clarify anarcat's change

Browse source 
v7 does not need to be done simulantaneously unless you choose to use
the new unlocked files feature
This commit is contained in:
Joey Hess 2018-12-05 12:22:36 -04:00
parent 8f1701a440
commit e658010128
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1 changed files with 8 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

20
doc/upgrades.mdwn
View file

@ -44,10 +44,6 @@ 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)
@ -59,14 +55,16 @@ Run `git-annex upgrade` to perform the upgrade.
v6 repositories are automatically upgraded to v7. v6 repositories are automatically upgraded to v7.
The only difference between v6 and v7 is that some additional git hooks The only difference between v6 and v7 is that some additional git hooks
were added in v7. were added in v7. See below for details about what's new in v6/v7.
## v5 -> v6 (git-annex version 6.x) ## v5 -> v6 (git-annex version 6.x)
A v6 git-annex repository can have some files locked while other files are A v6 git-annex repository can have some files locked while other files are
unlocked, and all git and git-annex commands can be used on both locked and unlocked, and all git and git-annex commands can be used on both locked and
unlocked files. (Although for locked files to be accessible, the filesystem unlocked files. It's a good idea to make sure that all users of the
must support symbolic links.) repository have upgraded git-annex and upgraded their repositories
to the new version before starting to use this feature, since old
versions of git-annex will ignore the new unlocked files.
Direct mode repositories are upgraded to instead use the new Direct mode repositories are upgraded to instead use the new
[[adjusted branches feature|git-annex-adjust]], which transparently unlocks [[adjusted branches feature|git-annex-adjust]], which transparently unlocks
@ -81,11 +79,9 @@ The behavior of some commands changes in an upgraded repository:
`git config annex.largefiles "largerthan=100kb and not (include=*.c or include=*.h)"` `git config annex.largefiles "largerthan=100kb and not (include=*.c or include=*.h)"`
* `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 change,
that will impact all clones of the repository. This means all clones of the
If you commit the unlocked files change, this will impact all clones of the repository will need to run at least v6 to correctly synchronise.
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