From 79b3e0dca944715a42f979000eb7009a01f5665a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 22 Mar 2021 13:43:58 -0400 Subject: [PATCH] comment --- ...t_3_ed4137413812467d67dd84aa5fde6263._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/forum/replacing_a_locked_file_without_unlocking_first/comment_3_ed4137413812467d67dd84aa5fde6263._comment diff --git a/doc/forum/replacing_a_locked_file_without_unlocking_first/comment_3_ed4137413812467d67dd84aa5fde6263._comment b/doc/forum/replacing_a_locked_file_without_unlocking_first/comment_3_ed4137413812467d67dd84aa5fde6263._comment new file mode 100644 index 0000000000..b61cf21404 --- /dev/null +++ b/doc/forum/replacing_a_locked_file_without_unlocking_first/comment_3_ed4137413812467d67dd84aa5fde6263._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2021-03-22T17:16:14Z" + content=""" +It's not even necessary to delete the symlink, you can just +rename the new version of the file over it. + +Unlocking the file is only necessary if you want to edit it in place. + +Unlocking a file does add a little bit of overhead. Mostly making +a copy of it that is not needed when you're just going to overwrite it. +Also the annex pointer gets added as a git object (which will get garbage +collected eventually) and some minor things get stored to git-annex's +internal database to keep track of it. +"""]]