doc/bugs/Weird_behaviour_of_direct_and_indirect_annexes.mdwn

@@ -0,0 +1,46 @@
+## What steps will reproduce the problem?
+
+    ~$ git annex webapp
+
+
+* Add Another Local Repository (~/Direct) "Direct", keep separate (from existing repo) no repo type
+* Add Repository, ~/Indirect "Indirect", combine (with Direct) , repo type client
+* Syncing enabled on both
+
+Then
+
+    ~/Indirect$ git annex indirect
+    commit  ok
+    indirect  ok
+    ok
+    ~/Indirect$ touch ../Direct/Test.File
+    
+
+## What is the expected output? What do you see instead?
+
+That ~/Indirect/Test.File be a symlink into .git/annex/objects/.......
+
+Instead, it is not a symlink. However, doing
+
+    ~/Indirect$ git annex direct
+    ~/Indirect$ git annex indirect
+
+results in what I would expect (until the content of Direct/Test.File is changed, when it ceases to be a symlink in ~/Indirect once more)
+
+## What version of git-annex are you using? On what operating system?
+git-annex version: 4.20130405
+
+Ubuntu 12.10
+
+
+## Please provide any additional information below.
+
+Reading [[direct_mode]], I thought that I could have two repos on my computer, one direct, and one indirect, and if running the assistant, that I could gain the security of retaining old versions, as well as the convenience of direct mode. (I think I understand that correctly; if a direct-mode file only exists in one repository, and is edited, the old version is lost, but if it is in multiple repos, then the old versions will be retained).
+
+It seems to me that if I do
+
+    ~/Direct$ echo Content > Test.File
+    ~/Direct$ echo More Content > Test.File
+    ~/Direct$ echo Even More Content > Test.File
+
+that all three copies are stored in ~/Indirect, so the functionality I'm after seems to work. However, ~/Indirect/Test.File ends up not being a symlink, which I think is odd/unexpected.