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

move aside to better place

Browse source
This commit is contained in:
Joey Hess 2016-01-14 18:19:00 -04:00
parent a47480b0da
commit 379004e3e7
Failed to extract signature
1 changed files with 5 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

10
doc/tips/unlocked_files.mdwn
View file

@ -114,11 +114,6 @@ old versions of files is an important part of git after all!
That's a good safe default. But there are ways to use git-annex that That's a good safe default. But there are ways to use git-annex that
make the second copy not be worth keeping: make the second copy not be worth keeping:
[[!template id=note text="""
When a [[direct_mode]] repository is upgraded, annex.thin is automatically
set, because direct mode made the same single-copy tradeoff.
"""]]
* When you're using git-annex to sync the current version of files across * When you're using git-annex to sync the current version of files across
devices, and don't care much about previous versions. devices, and don't care much about previous versions.
* When you have set up a backup repository, and use git-annex to copy * When you have set up a backup repository, and use git-annex to copy
@ -142,6 +137,11 @@ hard links. Ie, not Windows, and not FAT filesystems.
Setting annex.thin can save a lot of disk space, but it's a tradeoff Setting annex.thin can save a lot of disk space, but it's a tradeoff
between disk usage and safety. between disk usage and safety.
[[!template id=note text="""
When a [[direct_mode]] repository is upgraded, annex.thin is automatically
set, because direct mode made the same single-copy tradeoff.
"""]]
Keeping files locked is safer and also avoids using unnecessary Keeping files locked is safer and also avoids using unnecessary
disk space, but trades off easy modification of files. disk space, but trades off easy modification of files.