summaryrefslogtreecommitdiff
path: root/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
diff options
context:
space:
mode:
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.mdwn32
1 files changed, 0 insertions, 32 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
deleted file mode 100644
index 4a3329326..000000000
--- a/doc/bugs/Possible_data_loss_-_git_status___39__typechange__39___and_direct_mode.mdwn
+++ /dev/null
@@ -1,32 +0,0 @@
-#### 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.
-
-> This was the pre-commit hook, made it not run in direct mode. [[done]]
->
-> However, it's normal to see typechanged files in direct mode, and many
-> git commands that manipulate files in the working tree *can* result in
-> data loss. This is documented on [[direct_mode]].
-> --[[Joey]]