summaryrefslogtreecommitdiff
path: root/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
diff options
context:
space:
mode:
authorGravatar http://a-or-b.myopenid.com/ <http://a-or-b.myopenid.com/@web>2013-01-17 02:11:45 +0000
committerGravatar admin <admin@branchable.com>2013-01-17 02:11:45 +0000
commit734e7bae61339ca58c13e1de4c928c02cf66a31e (patch)
treebbecb81dd8d86cebe9bf9d2f80d14ae26700d1d2 /doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
parent81d08a689db2faf5146af3b0ab4e697ab219f893 (diff)
Diffstat (limited to 'doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn')
-rw-r--r--doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn27
1 files changed, 27 insertions, 0 deletions
diff --git a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn b/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
new file mode 100644
index 000000000..18fd1c291
--- /dev/null
+++ b/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
@@ -0,0 +1,27 @@
+#### What steps will reproduce the problem?
+
+When moving to direct mode files get flagged in git as 'typechange'.
+
+ md test-directmode; cd test-directmode ; git init; git annex init
+ date > test.file ; git annex add test.file
+ git commit -m "Initial commit"
+ git status # All fine
+ git annex direct
+ git status # typechange: test.file
+ git add test.file && git commit -m "looks like I should commit this"
+ # And the symlink is now broken...
+
+#### What is the expected output? What do you see instead?
+
+Surprised to see the typechange status in git. Would not expect to see anything, however, if you `git add` and then commit you can get data loss. :-(
+
+
+#### What version of git-annex are you using? On what operating system?
+
+git-annex version: 3.20130114
+
+OS: OSX 10.6.8
+
+#### Please provide any additional information below.
+
+