Added a comment: Rationale behind deleting and readding the symlinks on a move or...

diff --git a/doc/forum/What_is_the_best_way_to___34__git_annex_mv__34___file__63__/comment_2_9f7daf0a3e53b2cf64b2b64ca6fbfd9b._comment b/doc/forum/What_is_the_best_way_to___34__git_annex_mv__34___file__63__/comment_2_9f7daf0a3e53b2cf64b2b64ca6fbfd9b._comment
new file mode 100644 (file)
index 0000000..b21a63d
--- /dev/null
+++ b/doc/forum/What_is_the_best_way_to___34__git_annex_mv__34___file__63__/comment_2_9f7daf0a3e53b2cf64b2b64ca6fbfd9b._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="cardoso-neto"
+ avatar="http://cdn.libravatar.org/avatar/d90a656df072f3a29da54302c190c696"
+ subject="Rationale behind deleting and readding the symlinks on a move or rename"
+ date="2020-08-20T18:36:47Z"
+ content="""
+I couldn't find an explanation for this using the search bar, so I thought this would be as good a place as any to ask this.
+
+Even when I run `git mv` on git annexed file, git annex always changes it for what looks like a combo of `git rm old_symlink; git add new_symlink`
+
+I guess it does this when that pre-commit hook you mentioned runs.
+Why?
+"""]]