From 6b444926901802733ba2cc5159ad9b1248468573 Mon Sep 17 00:00:00 2001 From: "chocolate.camera@ec2ecab153906be21ac5f36652c33786ad0e0b60" Date: Mon, 31 Dec 2018 16:41:09 +0000 Subject: [PATCH] Added a comment --- ...omment_1_d7f38f681be51db1244988847840d735._comment | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/git-annex-unlock/comment_1_d7f38f681be51db1244988847840d735._comment diff --git a/doc/git-annex-unlock/comment_1_d7f38f681be51db1244988847840d735._comment b/doc/git-annex-unlock/comment_1_d7f38f681be51db1244988847840d735._comment new file mode 100644 index 0000000000..ee9d313622 --- /dev/null +++ b/doc/git-annex-unlock/comment_1_d7f38f681be51db1244988847840d735._comment @@ -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? +"""]]