From 3de6dffd36b291506bfb60ee1ffc224f8770ff4f Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 8 Oct 2019 14:32:42 -0400 Subject: [PATCH] comment --- ...nt_8_4be8e5f5bd30e512995563ce7098c983._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/lets_discuss_git_add_behavior/comment_8_4be8e5f5bd30e512995563ce7098c983._comment diff --git a/doc/forum/lets_discuss_git_add_behavior/comment_8_4be8e5f5bd30e512995563ce7098c983._comment b/doc/forum/lets_discuss_git_add_behavior/comment_8_4be8e5f5bd30e512995563ce7098c983._comment new file mode 100644 index 0000000000..8330e9ad80 --- /dev/null +++ b/doc/forum/lets_discuss_git_add_behavior/comment_8_4be8e5f5bd30e512995563ce7098c983._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 8""" + date="2019-10-08T18:03:05Z" + content=""" +Candyangel, you missed this part of my comment: + +> But `mv foo bar; git add bar` is normally identical to `git mv foo bar`. +> Why should using git-annex break that identity? + +With locked files, that identity still holds; you can mv a symlink and git +add it, and you again have an annexed file. So every git and git-annex +repository has always behaved that way. There are innumerable workflows and +documentation that depend on that, in big or small ways. +"""]]