aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2014-07-03 15:04:16 -0400
committerGravatar Joey Hess <joey@kitenet.net>2014-07-03 15:04:16 -0400
commit735e616de9f7f93ed04c32b3990195203a9be0bb (patch)
treebd54bb343957c25f8ee0fc943a4c4426197e7dcf
parent4e339e8a4183254b20d621696d69c6ccf08dab5b (diff)
close
-rw-r--r--doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn b/doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn
index 8692b93b6..66a199e8c 100644
--- a/doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn
+++ b/doc/bugs/git_mv_before_commit_breaks_symlinks.mdwn
@@ -12,3 +12,17 @@ When I `git mv` a file that I just `git annex add`-ed without having `git commit
### What version of git-annex are you using? On what operating system?
5.20140529 on Debian testing
+
+> This is fundamentally something git-annex cannot deal with,
+> because there is no way to hook into git to fix the symlink when
+> `git mv` moves the file.
+>
+> Instead, git-annex has several "good enough" fixes for the problem:
+>
+> * As soon as you `git commit`, the pre-commit hook will run `git annex
+> fix` and this will fix the symlink before it gets committed.
+> * You can run `git annex fix` yourself after `git mv`.
+> * Even `git annex add $file` will fix the symlink if the file is already
+> annexed.
+>
+> So, [[done]] --[[Joey]]