From 56e6da9ca478954ed6d73c6dd3e37f6c0305322e Mon Sep 17 00:00:00 2001 From: Lukey Date: Sat, 20 Mar 2021 17:42:09 +0000 Subject: [PATCH] Added a comment --- .../comment_1_637598d027bc6194dad89d63aea511d4._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/replacing_a_locked_file_without_unlocking_first/comment_1_637598d027bc6194dad89d63aea511d4._comment diff --git a/doc/forum/replacing_a_locked_file_without_unlocking_first/comment_1_637598d027bc6194dad89d63aea511d4._comment b/doc/forum/replacing_a_locked_file_without_unlocking_first/comment_1_637598d027bc6194dad89d63aea511d4._comment new file mode 100644 index 0000000000..41227e1886 --- /dev/null +++ b/doc/forum/replacing_a_locked_file_without_unlocking_first/comment_1_637598d027bc6194dad89d63aea511d4._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="Lukey" + avatar="http://cdn.libravatar.org/avatar/c7c08e2efd29c692cc017c4a4ca3406b" + subject="comment 1" + date="2021-03-20T17:42:06Z" + content=""" +I can't think of any problems, as the end-result is the same. ´git annex unlock´ also just removes the symlink and copies the (old)file into it's place. There's no state about this kept anywhere else. So whether you unlock the file and then replace it, or directly replace the symlink with the new file, ´git annex add´ afterwards sees exactly the same state of the worktree. +"""]]