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

Added a comment

Browse source
This commit is contained in:
chocolate.camera@ec2ecab153906be21ac5f36652c33786ad0e0b60 2018-12-31 16:41:09 +00:00 • committed by admin
parent 25cc890be1
commit 6b44492690
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
doc/git-annex-unlock/comment_1_d7f38f681be51db1244988847840d735._comment Normal file
View file

@ -0,0 +1,11 @@
[[!comment format=mdwn
username="chocolate.camera@ec2ecab153906be21ac5f36652c33786ad0e0b60"
nickname="chocolate.camera"
avatar="http://cdn.libravatar.org/avatar/4f00dfc3ad590ef7492788b854ceba78"
subject="comment 1"
date="2018-12-31T16:41:08Z"
content="""
> Normally, unlocking a file requires a copy to be made of its content, so that its original content is preserved
Does that imply than, on v7 in a file system that does not support hard links such as FAT32, `git annex adjust --unlock` would effectively be creating a duplicate of all files via cp (which is incredibly costly time-wise specially for big repos and huge files) and would effectively double the size it occupies?
"""]]