summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Joey Hess <joey@kitenet.net>2013-02-05 14:05:24 -0400
committerGravatar Joey Hess <joey@kitenet.net>2013-02-05 15:04:25 -0400
commitea341c1e994ad61ff130a1c76d00bfdd42a2bc8f (patch)
treeef34c43f0f67b206751c3627a62841d1ef1879ad
parent618c9513f5599fe89be1624e6379818f05f9925b (diff)
bug
-rw-r--r--doc/bugs/direct_mode_renames.mdwn10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/direct_mode_renames.mdwn b/doc/bugs/direct_mode_renames.mdwn
new file mode 100644
index 000000000..788c615dc
--- /dev/null
+++ b/doc/bugs/direct_mode_renames.mdwn
@@ -0,0 +1,10 @@
+When in direct mode, renaming a file with `git mv` does not update the
+direct mode mapping to use the new filename. This can lead to unexpected
+behavior later. `fsck` will correct the mapping. --[[Joey]]
+
+Perhaps the pre-commit hook needs to update the mapping for files that were
+deleted or added. This would allow manual `git mv` (and `git rm`) to work.
+
+This also affects moves of files when the assistant is being used.
+In this case, the assistant updates the mapping to add the new name,
+but does not delete the old name from the mapping.