diff options
author | Joey Hess <joeyh@joeyh.name> | 2015-12-27 15:59:59 -0400 |
---|---|---|
committer | Joey Hess <joeyh@joeyh.name> | 2015-12-27 15:59:59 -0400 |
commit | 60c88820987596809091ee010e6be2a083888bc8 (patch) | |
tree | dc2540c6deadfcf3efee1fd95948bcbd6f219db5 /doc/upgrades.mdwn | |
parent | 17490f3685aee698e10555c5dc3e915a317c2250 (diff) |
annex.thin
Decided it's too scary to make v6 unlocked files have 1 copy by default,
but that should be available to those who need it. This is consistent with
git-annex not dropping unused content without --force, etc.
* Added annex.thin setting, which makes unlocked files in v6 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 local
(and possibly only) copy of the old version.
* Enable annex.thin by default on upgrade from direct mode to v6, since
direct mode made the same tradeoff.
* fix: Adjusts unlocked files as configured by annex.thin.
Diffstat (limited to 'doc/upgrades.mdwn')
-rw-r--r-- | doc/upgrades.mdwn | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/doc/upgrades.mdwn b/doc/upgrades.mdwn index 9d30c2f14..b3deab715 100644 --- a/doc/upgrades.mdwn +++ b/doc/upgrades.mdwn @@ -72,10 +72,6 @@ The behavior of some commands changes in an upgraded repository: * `git annex unlock` and `git annex lock` change how the pointer to the annexed content is stored in git. -If a repository is only used in indirect mode, you can use git-annex -v5 and v6 in different clones of the same indirect mode repository without -problems. - On upgrade, all files in a direct mode repository will be converted to unlocked files. The upgrade will stage changes to all annexed files in the git repository, which you can then commit. |