Merge branch 'master' of ssh://git-annex.branchable.com

11 files changed, 893 insertions, 0 deletions

diff --git a/doc/bugs/Offline_editing_in_Android_removes_files_and_creates_links.mdwn b/doc/bugs/Offline_editing_in_Android_removes_files_and_creates_links.mdwn
new file mode 100644
index 000000000..9dd05d1d4
--- /dev/null
+++ b/doc/bugs/Offline_editing_in_Android_removes_files_and_creates_links.mdwn
@@ -0,0 +1,45 @@
+### Please describe the problem.
+Two androids, A and B, and a computer, C. All running git annex assistant.
+If you edit a file on A while A is offline, when A is back online and reconnects, that file will disappear from C and, in B, it will be substituted by a link
+If you create a new file on A, that file will appear as a link in B and in C
+
+
+### What steps will reproduce the problem?
+- Have A, B, and C be connected sharing some repo. Create a file, file1. Let it propagate, so file1 is on A, B, C.
+
+- Take A offline (e.g., turn wifi off).
+
+- Edit file1 in A.
+
+- Create file2 in A.
+
+- (Let those files appear in the repo in A as in
+[2015-02-27 20:55:04 CET] Committer: Adding file1
+add file1 ok
+)
+
+- Turn the wifi of A on again.
+
+- Sync A from the webapp (clik on sync now)
+
+- In B (the other android) both file1 and file2 will contain just links, not the actual content of file1 and file2.
+
+- In the computer, file1 will have disappeared and file2 will be a link that points nowhere. (The link that file2 points too, as a string, are the contents of file2 in B). 
+
+
+
+### What version of git-annex are you using? On what operating system?
+Computer: 5.20141125 
+
+Androids: 5.20150226-g9c72d37 and 5.20150224-g9dca034
+
+
+### Please provide any additional information below.
+
+[[!format sh """
+# If you can, paste a complete transcript of the problem occurring here.
+# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+
+
+# End of transcript or log.
+"""]]
diff --git a/doc/bugs/Offline_editing_in_Android_removes_files_and_creates_links/comment_1_a15eb9cd1a7bcdfa4b16459ef978a019._comment b/doc/bugs/Offline_editing_in_Android_removes_files_and_creates_links/comment_1_a15eb9cd1a7bcdfa4b16459ef978a019._comment
new file mode 100644
index 000000000..236f7f07d
--- /dev/null
+++ b/doc/bugs/Offline_editing_in_Android_removes_files_and_creates_links/comment_1_a15eb9cd1a7bcdfa4b16459ef978a019._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnbPKLjBONawBd74MKJZo05juCqdsP1jAU"
+ nickname="Ramon"
+ subject="comment 1"
+ date="2015-02-27T22:06:51Z"
+ content="""
+I can confirm the above using, in the computer 
+
+5.20150219-g52daae5 
+
+and 5.20150226-g9c72d37
+
+In the computer, files that were edited in the Android while offline, might not always disappear, but might reappear as content after first being shown as links that point nowhere. Or may remain as links that point nowhere.
+
+In the Androids files that contain links (instead of original content) continue containint the links for over 1 hour.
+
+Binary (e.g., PDFs) and plain text files do not always behave the same. Plain text files are more easily affected (whereas PDFs are back to what they should be sooner).
+
+"""]]
diff --git a/doc/bugs/git_annex_wont_work_with_git-dir_and_work-tree/comment_2_fb75f5941d355947b3f06165825dd012._comment b/doc/bugs/git_annex_wont_work_with_git-dir_and_work-tree/comment_2_fb75f5941d355947b3f06165825dd012._comment
new file mode 100644
index 000000000..b71650099
--- /dev/null
+++ b/doc/bugs/git_annex_wont_work_with_git-dir_and_work-tree/comment_2_fb75f5941d355947b3f06165825dd012._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawlvmWVPaSpWJO5_rimCL0lEoJRoKOIjhHE"
+ nickname="Gioacchino"
+ subject="Why shoul git-annex support --git-dir"
+ date="2015-03-01T10:10:31Z"
+ content="""
+Hi!
+
+There are multiple use case as I explained on IRC and it is why I and probably more users need it, there are some git-annex repository that i share also with other programs like RetroShare and apache USERDIR (like http://efesto.eigenlab.org/~gioacchino/) i don't like .git directory to be shared by these programs as the file are publics but not the metadata stored on the .git ( http://efesto.eigenlab.org/~gioacchino/.git/config ) i know i can do that with other tricks like htaccess but it is application specific hack while the real solution is to keep the .git in a private place
+
+Another use case is when you are grepping or doing scripty stuff on your dir having the .git in another place allow you to do stuff without concern about what there is inside .git without using options like --exclude and similar
+
+The list of use cases can grow as they are all the one caused git to support --git-dir so for the sake of consistence and for your donors please propagate --git-dir on all git-annex components ;)
+
+P.S. I am not native english speaker so sorry if something sounds bad
+"""]]
diff --git a/doc/forum/Assistant:_run_with___34__sync_--fast__34___to_automatically_use_only_available_remotes.mdwn b/doc/forum/Assistant:_run_with___34__sync_--fast__34___to_automatically_use_only_available_remotes.mdwn
new file mode 100644
index 000000000..3a6e4a710
--- /dev/null
+++ b/doc/forum/Assistant:_run_with___34__sync_--fast__34___to_automatically_use_only_available_remotes.mdwn
@@ -0,0 +1,18 @@
+I have a set of machines, call them A, B, C, I am trying to keep synced. However, all three of them do not always see all the other two (e.g., I might need a vpn tunnel up to see C from A, etc, or C is down, etc). 
+Everything works as expected (i.e., content gets from one machine to the others) if in the webapp I disable the non-reachable nodes (or, equivalently, I set annex-sync to false in .git/config). But I wonder if there is a way to have git annex not use the non-reachable remotes. Using git-annex sync --fast does not seem to do it (since all remotes I guess have the same annex-cost value).
+
+
+I understand a possible solution involves using 
+
+```
+remote.<name>.annex-cost-command
+```
+
+so that I set the cost of the non-available remote to a large value. But then, I'd need to tell the assistant to always use, by default
+
+
+```
+git-annex sync --fast --content
+```
+
+and I do not know how to make it use "--fast". 
diff --git a/doc/forum/How_to_emulate___34__one-way_sync__34__s_in_a_direct_repo__63__/comment_4_d899cf35801636e618e4675d91d6104a._comment b/doc/forum/How_to_emulate___34__one-way_sync__34__s_in_a_direct_repo__63__/comment_4_d899cf35801636e618e4675d91d6104a._comment
new file mode 100644
index 000000000..146156b2d
--- /dev/null
+++ b/doc/forum/How_to_emulate___34__one-way_sync__34__s_in_a_direct_repo__63__/comment_4_d899cf35801636e618e4675d91d6104a._comment
@@ -0,0 +1,24 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnbPKLjBONawBd74MKJZo05juCqdsP1jAU"
+ nickname="Ramon"
+ subject="comment 4"
+ date="2015-03-01T23:58:19Z"
+ content="""
+But is there a way to have the changes in one node (the \"read only\") discarded when there are changes in the remote, so that the new version in the remote is propagated to the read only node?
+So I guess what I'd like is something like *update-changes-from-others.sh* (Like sync, but don't commit any local changes. Merge them like sync, don't discard) but without the merging, so discarding any changes as soon as a new version appears in the remote. 
+
+
+I've tried the ```remote.foo.annex-readonly = true``` in Android but I am not getting my intended behavior.
+
+For instance, suppose a computer and a Android device (but with direct mode, since working with assistant)
+
+- Create file in computer
+- Let it appear in Android
+- Modify in Android; this change apparently does not propagate back to the computer.
+- Modify again in computer; sometime later one gets a conflict (file.variant-xxxx and file-variant-yyyy, with the computer getting one of the conflicts as a link that points nowhere).
+
+
+Adding ```autocommit = false``` does not help either.
+
+
+"""]]
diff --git a/doc/forum/Huge_differences_in_sync_times_in_different_directories_of_same_machines.mdwn b/doc/forum/Huge_differences_in_sync_times_in_different_directories_of_same_machines.mdwn
new file mode 100644
index 000000000..c936fbd65
--- /dev/null
+++ b/doc/forum/Huge_differences_in_sync_times_in_different_directories_of_same_machines.mdwn
@@ -0,0 +1,127 @@
+I am confused by the differences in the time between updates of different
+repositories in the same machines and of the same repository in different
+machines. I am using the assistant (in all machines, 
+'git annex assitant --autostart').
+
+
+
+For instance, I have three machines synced as
+
+A <-> B <-> C
+
+and I have two directories being synced. The configuration (except for
+directory names) is the same and looks like
+
+
+```
+[annex]
+        uuid = something
+        version = 5
+        direct = true
+        autoupgrade = true
+        autocommit = true
+        startupscan = true
+[remote "machine_repo"]
+        url = ssh://xxxxxx/~/repo/
+        fetch = +refs/heads/*:refs/remotes/machine_repo/*
+        annex-uuid = xxxxxxxxxxxxx
+
+```
+
+
+I modify or add a file in one of the directories in A, and it quickly
+(less than 30 seconds) appears in B and shortly after that in C.
+
+In another directory, however, more than 30 minutes can go by without C
+ever changing (even if B gets the change almost immediately). Looking at
+the logs I cannot understand what is happening. This is the case of a
+file, ```A_sentinel_file_A ```, created at 01:46.
+
+In B (where it appears almost immediately)  I can see
+
+
+```
+[2015-03-02 01:46:17 CET] Pusher: Syncing with 123.456.789.101_somedir 
+To ssh://ramon@git-annex-Machine_C-ramon_22_annex.2Done.2Dway.2F/~/some-dir/
+   794df9f..ae8c3f0  git-annex -> synced/git-annex
+Automatic merge went well; stopped before committing as requested
+[2015-03-02 01:47:03 CET] Committer: Committing changes to git
+[2015-03-02 01:47:03 CET] Pusher: Syncing with 123.456.789.101_somedir 
+
+A_sentinel_file_A
+             18 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)
+[2015-03-02 01:47:04 CET] Transferrer: Uploaded A_sentinel_file_A
+To ssh://ramon@git-annex-Machine_C-ramon_22_annex.2Done.2Dway.2F/~/some-dir/
+   ae8c3f0..b043335  git-annex -> synced/git-annex
+   75269bc..b61c7a5  annex/direct/master -> synced/master
+[2015-03-02 01:47:04 CET] Committer: Committing changes to git
+[2015-03-02 01:47:06 CET] Pusher: Syncing with 123.456.789.101_somedir 
+To ssh://ramon@git-annex-Machine_C-ramon_22_annex.2Done.2Dway.2F/~/some-dir/
+   b043335..fc9279c  git-annex -> synced/git-annex
+```
+
+
+And in C (the machine with IP 123.456.789.101, above)  I can see
+
+
+```
+[2015-03-02 01:46:13 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   593d908..794df9f  git-annex  -> Machine_B_somedir/git-annex
+   593d908..235149d  synced/git-annex -> Machine_B_somedir/synced/git-annex
+   a1596b3..75269bc  synced/master -> Machine_B_somedir/synced/master
+[2015-03-02 01:46:17 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   a1596b3..75269bc  annex/direct/master -> Machine_B_somedir/annex/direct/master
+   794df9f..ae8c3f0  git-annex  -> Machine_B_somedir/git-annex
+   a1596b3..75269bc  master     -> Machine_B_somedir/master
+[2015-03-02 01:46:27 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   ae8c3f0..632caa4  git-annex  -> Machine_B_somedir/git-annex
+   235149d..632caa4  synced/git-annex -> Machine_B_somedir/synced/git-annex
+[2015-03-02 01:47:02 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   632caa4..56ac968  synced/git-annex -> Machine_B_somedir/synced/git-annex
+   75269bc..b61c7a5  synced/master -> Machine_B_somedir/synced/master
+[2015-03-02 01:47:02 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   632caa4..b043335  git-annex  -> Machine_B_somedir/git-annex
+[2015-03-02 01:47:07 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   75269bc..b61c7a5  annex/direct/master -> Machine_B_somedir/annex/direct/master
+   b043335..fc9279c  git-annex  -> Machine_B_somedir/git-annex
+   75269bc..b61c7a5  master     -> Machine_B_somedir/master
+[2015-03-02 01:47:15 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   fc9279c..a4642a8  git-annex  -> Machine_B_somedir/git-annex
+   56ac968..a4642a8  synced/git-annex -> Machine_B_somedir/synced/git-annex
+(merging synced/git-annex Machine_B_somedir/git-annex into git-annex...)
+(recording state in git...)
+[2015-03-02 02:17:23 CET] RemoteControl: Syncing with Machine_B_somedir 
+From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+   a4642a8..bfaba72  git-annex  -> Machine_B_somedir/git-annex
+   a4642a8..bfaba72  synced/git-annex -> Machine_B_somedir/synced/git-annex
+   b61c7a5..29ff91e  synced/master -> Machine_B_somedir/synced/master   
+   
+```
+
+Why did Machine C did not show the updated file at 01:47, which is when, I
+think, machine B pushes it there? Or at 02:17 when both machines again
+seem to talk to each other? Regardless, at 02:27 the file still was not
+there. Yes, of course, if I issue a
+
+```
+git annex sync --content
+```
+
+then the file is shown in Machine C. But I should not need to do that.
+
+
+
+In contrast, as I said, there is another directory, with identical
+configuration, where these things do not happen and changes show
+immediately (both directories, for now, only have tiny test files).
+
+What am I doing wrong? This is too big a difference to make sense to me.
+
+
diff --git a/doc/forum/Huge_differences_in_sync_times_in_different_directories_of_same_machines/comment_1_445766c0f646e9cb5b45b863ad87e85a._comment b/doc/forum/Huge_differences_in_sync_times_in_different_directories_of_same_machines/comment_1_445766c0f646e9cb5b45b863ad87e85a._comment
new file mode 100644
index 000000000..5c1ddf127
--- /dev/null
+++ b/doc/forum/Huge_differences_in_sync_times_in_different_directories_of_same_machines/comment_1_445766c0f646e9cb5b45b863ad87e85a._comment
@@ -0,0 +1,136 @@
+[[!comment format=mdwn
+ username="https://www.google.com/accounts/o8/id?id=AItOawnbPKLjBONawBd74MKJZo05juCqdsP1jAU"
+ nickname="Ramon"
+ subject="comment 1"
+ date="2015-03-02T01:47:32Z"
+ content="""
+Ooops, the formatting got all messed up. Here it is again:
+
+I am confused by the differences in the time between updates of different
+repositories in the same machines and of the same repository in different
+machines. I am using the assistant (in all machines, 
+'git annex assitant --autostart').
+
+
+
+For instance, I have three machines synced as
+
+A <-> B <-> C
+
+and I have two directories being synced. The configuration (except for
+directory names) is the same and looks like
+
+
+
+    [annex]
+            uuid = something
+            version = 5
+            direct = true
+            autoupgrade = true
+            autocommit = true
+            startupscan = true
+    [remote \"machine_repo\"]
+            url = ssh://xxxxxx/~/repo/
+            fetch = +refs/heads/*:refs/remotes/machine_repo/*
+            annex-uuid = xxxxxxxxxxxxx
+    
+
+
+
+I modify or add a file in one of the directories in A, and it quickly
+(less than 30 seconds) appears in B and shortly after that in C.
+
+In another directory, however, more than 30 minutes can go by without C
+ever changing (even if B gets the change almost immediately). Looking at
+the logs I cannot understand what is happening. This is the case of a
+file, ```A_sentinel_file_A ```, created at 01:46.
+
+In B (where it appears almost immediately)  I can see
+
+
+    [2015-03-02 01:46:17 CET] Pusher: Syncing with 123.456.789.101_somedir 
+    To ssh://ramon@git-annex-Machine_C-ramon_22_annex.2Done.2Dway.2F/~/some-dir/
+       794df9f..ae8c3f0  git-annex -> synced/git-annex
+    Automatic merge went well; stopped before committing as requested
+    [2015-03-02 01:47:03 CET] Committer: Committing changes to git
+    [2015-03-02 01:47:03 CET] Pusher: Syncing with 123.456.789.101_somedir 
+    
+    A_sentinel_file_A
+                 18 100%    0.00kB/s    0:00:00 (xfr#1, to-chk=0/1)
+    [2015-03-02 01:47:04 CET] Transferrer: Uploaded A_sentinel_file_A
+    To ssh://ramon@git-annex-Machine_C-ramon_22_annex.2Done.2Dway.2F/~/some-dir/
+       ae8c3f0..b043335  git-annex -> synced/git-annex
+       75269bc..b61c7a5  annex/direct/master -> synced/master
+    [2015-03-02 01:47:04 CET] Committer: Committing changes to git
+    [2015-03-02 01:47:06 CET] Pusher: Syncing with 123.456.789.101_somedir 
+    To ssh://ramon@git-annex-Machine_C-ramon_22_annex.2Done.2Dway.2F/~/some-dir/
+       b043335..fc9279c  git-annex -> synced/git-annex
+
+
+
+And in C (the machine with IP 123.456.789.101, above)  I can see
+
+
+
+    [2015-03-02 01:46:13 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       593d908..794df9f  git-annex  -> Machine_B_somedir/git-annex
+       593d908..235149d  synced/git-annex -> Machine_B_somedir/synced/git-annex
+       a1596b3..75269bc  synced/master -> Machine_B_somedir/synced/master
+    [2015-03-02 01:46:17 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       a1596b3..75269bc  annex/direct/master -> Machine_B_somedir/annex/direct/master
+       794df9f..ae8c3f0  git-annex  -> Machine_B_somedir/git-annex
+       a1596b3..75269bc  master     -> Machine_B_somedir/master
+    [2015-03-02 01:46:27 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       ae8c3f0..632caa4  git-annex  -> Machine_B_somedir/git-annex
+       235149d..632caa4  synced/git-annex -> Machine_B_somedir/synced/git-annex
+    [2015-03-02 01:47:02 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       632caa4..56ac968  synced/git-annex -> Machine_B_somedir/synced/git-annex
+       75269bc..b61c7a5  synced/master -> Machine_B_somedir/synced/master
+    [2015-03-02 01:47:02 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       632caa4..b043335  git-annex  -> Machine_B_somedir/git-annex
+    [2015-03-02 01:47:07 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       75269bc..b61c7a5  annex/direct/master -> Machine_B_somedir/annex/direct/master
+       b043335..fc9279c  git-annex  -> Machine_B_somedir/git-annex
+       75269bc..b61c7a5  master     -> Machine_B_somedir/master
+    [2015-03-02 01:47:15 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       fc9279c..a4642a8  git-annex  -> Machine_B_somedir/git-annex
+       56ac968..a4642a8  synced/git-annex -> Machine_B_somedir/synced/git-annex
+    (merging synced/git-annex Machine_B_somedir/git-annex into git-annex...)
+    (recording state in git...)
+    [2015-03-02 02:17:23 CET] RemoteControl: Syncing with Machine_B_somedir 
+    From ssh://git-annex-Machine_B-ramon_22_annex.2Done.2Dway/~/some-dir
+       a4642a8..bfaba72  git-annex  -> Machine_B_somedir/git-annex
+       a4642a8..bfaba72  synced/git-annex -> Machine_B_somedir/synced/git-annex
+       b61c7a5..29ff91e  synced/master -> Machine_B_somedir/synced/master   
+       
+
+
+Why did Machine C did not show the updated file at 01:47, which is when, I
+think, machine B pushes it there? Or at 02:17 when both machines again
+seem to talk to each other? Regardless, at 02:27 the file still was not
+there. Yes, of course, if I issue a
+
+```
+    git annex sync --content
+```
+
+then the file is shown in Machine C. But I should not need to do that.
+
+
+
+In contrast, as I said, there is another directory, with identical
+configuration, where these things do not happen and changes show
+immediately (both directories, for now, only have tiny test files).
+
+
+
+
+
+"""]]
diff --git a/doc/forum/Verification/comment_2_7df45d1e20a32458791603d5b9fe3dc4._comment b/doc/forum/Verification/comment_2_7df45d1e20a32458791603d5b9fe3dc4._comment
new file mode 100644
index 000000000..c98a210b6
--- /dev/null
+++ b/doc/forum/Verification/comment_2_7df45d1e20a32458791603d5b9fe3dc4._comment
@@ -0,0 +1,15 @@
+[[!comment format=mdwn
+ username="Régis"
+ subject="comment 2"
+ date="2015-02-27T21:38:05Z"
+ content="""
+Thanks for this speedy answer !
+
+I have version 5.20150219 installed on all the clients and on the server.
+The ssh server is a gcrypt repository. Could this be the reason of the clients not being notificated of the  changes ??
+
+Also, in theory, some file on one of the repositories could get corrupted, deleted, whatever. How can I make the repo check if everything is like intended on the other repos ? 
+For example, I made a test renaming a file within the objects directory on the remote ssh server and ran git annex fchk, but it reported nothing...
+
+Many thanks again !
+"""]]
diff --git a/doc/forum/Verification/comment_3_74db3ec8b03f48912306e48b8d5f7242._comment b/doc/forum/Verification/comment_3_74db3ec8b03f48912306e48b8d5f7242._comment
new file mode 100644
index 000000000..962707277
--- /dev/null
+++ b/doc/forum/Verification/comment_3_74db3ec8b03f48912306e48b8d5f7242._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="Régis"
+ subject="comment 3"
+ date="2015-02-28T18:33:27Z"
+ content="""
+Also, I noted a difference between encrypted (gcrypt) repos and unencrypted repos. The second ones have the other icon saying that it is live messaging. The encrypted one have a standard icon.
+Is it a technical limitation that encrypted repos can not live message ? And could it be the reason why the sync is not happening itself until i manually choose \"sync\" from the menu ?
+"""]]
diff --git a/doc/forum/View_special_remote_information__63__.mdwn b/doc/forum/View_special_remote_information__63__.mdwn
new file mode 100644
index 000000000..31382040b
--- /dev/null
+++ b/doc/forum/View_special_remote_information__63__.mdwn
@@ -0,0 +1 @@
+How is it possible to view the URL etc of a special remote with git annex? I checked out a git annex repository and would like to know where the files where fetched from. 
diff --git a/doc/todo/Shorten_long_file_names_preventing_git_checkout.mdwn b/doc/todo/Shorten_long_file_names_preventing_git_checkout.mdwn
new file mode 100644
index 000000000..6f8a68d57
--- /dev/null
+++ b/doc/todo/Shorten_long_file_names_preventing_git_checkout.mdwn
@@ -0,0 +1,484 @@
+Submitting here from https://github.com/joeyh/git-annex/pull/36
+
+    commit 05b7e0d2e87c1c92df773d72ee0ac7c9638be058
+    Author: Eric OConnor <eric@oco.nnor.org>
+    Date:   Sat Feb 28 23:14:50 2015 -0700
+
+        Allow this repository to be checked out in filesystems with 255 char filename limits
+
+    diff --git a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known.mdwn b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known.mdwn
+    new file mode 100644
+    index 0000000..69732a7
+    --- /dev/null
+    +++ b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known.mdwn
+    @@ -0,0 +1,46 @@
+    +### Please describe the problem.
+    +
+    +
+    +some time ago i was using the webapp bound to a dedicated port number to get around firewall reconfig. Now after some time without using the webapp i'm using it again and when i start it with 
+    +
+    +     git-annex webapp --listen=192.168.21.12:46199
+    +
+    +it never starts but just keeps waiting forever(?) 
+    +
+    +Update:(to clarify - the following works fine but results in the "random" port "problem")
+    +
+    +    git-annex webapp --listen=192.168.21.12
+    +
+    +
+    +
+    +
+    +### What steps will reproduce the problem?
+    +
+    +
+    +git-annex webapp --listen=192.168.21.12:46199
+    +
+    +
+    +### What version of git-annex are you using? On what operating system?
+    +
+    +
+    +version 5.20140716-g8c14ba8 on debian wheezy using your pre build static tar archive. 
+    +
+    +### Please provide any additional information below.
+    +
+    +[[!format sh """
+    +# If you can, paste a complete transcript of the problem occurring here.
+    +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+    +
+    +
+    +the log output is the following 3 lines 
+    +
+    +[2014-07-23 16:41:45 CEST] main: starting assistant version 5.20140716-g8c14ba8
+    +WebApp crashed: getAddrInfo: does not exist (Name or service not known)
+    +[2014-07-23 16:41:45 CEST] WebApp: warning WebApp crashed: getAddrInfo: does not exist (Name or service not known)
+    +
+    +
+    +
+    +# End of transcript or log.
+    +"""]]
+    +
+    +> [[done]] --[[Joey]] 
+    diff --git a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known/comment_1_4d1b96911e3e227c7433ccea543872c1._comment b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known/comment_1_4d1b96911e3e227c7433ccea543872c1._comment
+    new file mode 100644
+    index 0000000..5808c56
+    --- /dev/null
+    +++ b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known/comment_1_4d1b96911e3e227c7433ccea543872c1._comment
+    @@ -0,0 +1,10 @@
+    +[[!comment format=mdwn
+    + username="http://joeyh.name/"
+    + ip="24.159.78.125"
+    + subject="comment 1"
+    + date="2014-07-23T22:10:37Z"
+    + content="""
+    +Support for --listen with a port was removed in version 5.20140306, since it was buggy. In particular, when the webapp creates a new repository, it needs to switch to a new port to serve that repository, so specifying a single port won't work.
+    +
+    +Instead, when annex.listen or --listen specifies the address to listen on, `git annex webapp` will print out the url to use to open it, including the port it picked. This could be used in a script, or clicked on in the terminal to open a local browser when running the webapp on a remote host.
+    +"""]]
+    diff --git a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known/comment_2_7be98a630e1deb655a4d1675bf622d05._comment b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known/comment_2_7be98a630e1deb655a4d1675bf622d05._comment
+    new file mode 100644
+    index 0000000..2dd9885
+    --- /dev/null
+    +++ b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known/comment_2_7be98a630e1deb655a4d1675bf622d05._comment
+    @@ -0,0 +1,8 @@
+    +[[!comment format=mdwn
+    + username="markusk"
+    + ip="79.243.250.79"
+    + subject="comment 2"
+    + date="2014-07-23T23:18:37Z"
+    + content="""
+    +Thank you for the info! Will add the port grep to my auth grep script as you suggested. 
+    +"""]]
+    diff --git a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__.mdwn b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__.mdwn
+    deleted file mode 100644
+    index 69732a7..0000000
+    --- a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__.mdwn
+    +++ /dev/null
+    @@ -1,46 +0,0 @@
+    -### Please describe the problem.
+    -
+    -
+    -some time ago i was using the webapp bound to a dedicated port number to get around firewall reconfig. Now after some time without using the webapp i'm using it again and when i start it with 
+    -
+    -     git-annex webapp --listen=192.168.21.12:46199
+    -
+    -it never starts but just keeps waiting forever(?) 
+    -
+    -Update:(to clarify - the following works fine but results in the "random" port "problem")
+    -
+    -    git-annex webapp --listen=192.168.21.12
+    -
+    -
+    -
+    -
+    -### What steps will reproduce the problem?
+    -
+    -
+    -git-annex webapp --listen=192.168.21.12:46199
+    -
+    -
+    -### What version of git-annex are you using? On what operating system?
+    -
+    -
+    -version 5.20140716-g8c14ba8 on debian wheezy using your pre build static tar archive. 
+    -
+    -### Please provide any additional information below.
+    -
+    -[[!format sh """
+    -# If you can, paste a complete transcript of the problem occurring here.
+    -# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log
+    -
+    -
+    -the log output is the following 3 lines 
+    -
+    -[2014-07-23 16:41:45 CEST] main: starting assistant version 5.20140716-g8c14ba8
+    -WebApp crashed: getAddrInfo: does not exist (Name or service not known)
+    -[2014-07-23 16:41:45 CEST] WebApp: warning WebApp crashed: getAddrInfo: does not exist (Name or service not known)
+    -
+    -
+    -
+    -# End of transcript or log.
+    -"""]]
+    -
+    -> [[done]] --[[Joey]] 
+    diff --git a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__/comment_1_4d1b96911e3e227c7433ccea543872c1._comment b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__/comment_1_4d1b96911e3e227c7433ccea543872c1._comment
+    deleted file mode 100644
+    index 5808c56..0000000
+    --- a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__/comment_1_4d1b96911e3e227c7433ccea543872c1._comment
+    +++ /dev/null
+    @@ -1,10 +0,0 @@
+    -[[!comment format=mdwn
+    - username="http://joeyh.name/"
+    - ip="24.159.78.125"
+    - subject="comment 1"
+    - date="2014-07-23T22:10:37Z"
+    - content="""
+    -Support for --listen with a port was removed in version 5.20140306, since it was buggy. In particular, when the webapp creates a new repository, it needs to switch to a new port to serve that repository, so specifying a single port won't work.
+    -
+    -Instead, when annex.listen or --listen specifies the address to listen on, `git annex webapp` will print out the url to use to open it, including the port it picked. This could be used in a script, or clicked on in the terminal to open a local browser when running the webapp on a remote host.
+    -"""]]
+    diff --git a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__/comment_2_7be98a630e1deb655a4d1675bf622d05._comment b/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__/comment_2_7be98a630e1deb655a4d1675bf622d05._comment
+    deleted file mode 100644
+    index 2dd9885..0000000
+    --- a/doc/bugs/_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41_____91__2014-07-23_16:41:45_CEST__93___WebApp:_warning_WebApp_crashed:_getAddrInfo:_does_not_exist___40__Name_or_service_not_known__41__/comment_2_7be98a630e1deb655a4d1675bf622d05._comment
+    +++ /dev/null
+    @@ -1,8 +0,0 @@
+    -[[!comment format=mdwn
+    - username="markusk"
+    - ip="79.243.250.79"
+    - subject="comment 2"
+    - date="2014-07-23T23:18:37Z"
+    - content="""
+    -Thank you for the info! Will add the port grep to my auth grep script as you suggested. 
+    -"""]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47.mdwn b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47.mdwn
+    new file mode 100644
+    index 0000000..dae654d
+    --- /dev/null
+    +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47.mdwn
+    @@ -0,0 +1,63 @@
+    +### What steps will reproduce the problem?
+    +[[!format sh """
+    +C:\Users\Bruno>mkdir annex
+    +
+    +C:\Users\Bruno>cd annex
+    +
+    +C:\Users\Bruno\annex>git init
+    +Initialized empty Git repository in C:/Users/Bruno/annex/.git/
+    +
+    +C:\Users\Bruno\annex>git annex init
+    +init
+    +  Detected a crippled filesystem.
+    +
+    +  Enabling direct mode.
+    +
+    +  Detected a filesystem without fifo support.
+    +
+    +  Disabling ssh connection caching.
+    +ok
+    +(Recording state in git...)
+    +
+    +C:\Users\Bruno\annex>echo test > test
+    +
+    +C:\Users\Bruno\annex>git annex add .
+    +add test (checksum...) ok
+    +(Recording state in git...)
+    +
+    +C:\Users\Bruno\annex>git commit -a -m added
+    +[master (root-commit) 2eea610] added
+    + 1 file changed, 1 insertion(+)
+    + create mode 120000 test
+    +
+    +C:\Users\Bruno\annex>git annex sync
+    +(Recording state in git...)
+    +fatal: unable to access '../../../../C:\Users\Bruno\annex\.git/config': Invalid argument
+    +
+    +git-annex: user error (xargs ["-0","git","--git-dir=C:\\Users\\Bruno\\annex\\.git","--work-tree=C:\\Users\\Bruno\\annex","add","-f"] exited 123)
+    +failed
+    +git-annex: sync: 1 failed
+    +"""]]
+    +
+    +### What version of git-annex are you using? On what operating system?
+    +Windows 8 (64 bits)
+    +
+    +git version 1.8.4.msysgit.0
+    +
+    +[[!format sh """
+    +git-annex version: 4.20131008-ge115441
+    +build flags: Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash
+    +key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
+    +remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
+    +local repository version: 4
+    +default repository version: 3
+    +supported repository versions: 3 4
+    +upgrade supported from repository versions: 2
+    +"""]]
+    +
+    +### Please provide any additional information below.
+    +C:\Users\Bruno\annex\.git\config exists
+    +
+    +> xargs was one problem; also msysgit seems to just not
+    +> accept DOS style paths anymore in --git-dir or --git-work-tree.
+    +> megaweird. [[fixed|done]] --[[Joey]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment
+    new file mode 100644
+    index 0000000..cc616aa
+    --- /dev/null
+    +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment
+    @@ -0,0 +1,8 @@
+    +[[!comment format=mdwn
+    + username="http://joeyh.name/"
+    + ip="64.134.31.139"
+    + subject="comment 1"
+    + date="2013-10-16T20:42:07Z"
+    + content="""
+    +I don't know what to make of this bug report. You say that \"C:\Users\Bruno\annex.git\config\" exists, but you show the creation of a \"C:\Users\Bruno\annex\", and not the other repository. I cannot reproduce it, even if I first \"git init --bare annex.git\". 
+    +"""]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment
+    new file mode 100644
+    index 0000000..a40e9cb
+    --- /dev/null
+    +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment
+    @@ -0,0 +1,48 @@
+    +[[!comment format=mdwn
+    + username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM"
+    + nickname="Bruno"
+    + subject="comment 2"
+    + date="2013-10-16T22:47:46Z"
+    + content="""
+    +There's no other repo yet. I have the same problem when I try to sync between two repos but I simplified the instructions to reproduce the bug easily.
+    +
+    +Here's the instructions on Debian :
+    +[[!format sh \"\"\"
+    +bruno@debian:~$ mkdir annex
+    +bruno@debian:~$ cd annex
+    +bruno@debian:~/annex$ git init
+    +Initialized empty Dépôt git dans /home/bruno/annex/.git/
+    +bruno@debian:~/annex$ git annex init
+    +init  ok
+    +(Recording state in git...)
+    +bruno@debian:~/annex$ echo test > test
+    +bruno@debian:~/annex$ git annex add .
+    +add test (checksum...) ok
+    +(Recording state in git...)
+    +bruno@debian:~/annex$ git commit -a -m added
+    +[master (root-commit) 631049d] added
+    + 1 file changed, 1 insertion(+)
+    + create mode 120000 test
+    +bruno@debian:~/annex$ git annex sync
+    +commit
+    +ok
+    +bruno@debian:~/annex$\"\"\"]]
+    +
+    +It seems --git-dir wants 'c:/...' instead of 'c:\\...'.
+    +
+    +[[!format sh \"\"\"
+    +C:\Users\Bruno\annex>git --git-dir=C:\\Users\\Bruno\\annex\\.git --work-tree=C:\\Users\\Bruno\\annex add -f test
+    +fatal: unable to access '../../../../C:\\Users\\Bruno\\annex\\.git/config': Invalid argument
+    +
+    +C:\Users\Bruno\annex>git --git-dir=C:/Users/Bruno/annex/.git --work-tree=C:\\Users\\Bruno\\annex add -f test
+    +
+    +C:\Users\Bruno\annex>\"\"\"]]
+    +
+    +It's weird that I don't have any problem with the following command:
+    +[[!format sh \"\"\"C:\Users\Bruno\annex>git --git-dir=C:\\Users\\Bruno\\annex\\.git --work-tree=C:\\Users\\Bruno\\annex config -l
+    +core.symlinks=false
+    +core.autocrlf=true
+    +[...]\"\"\"]]
+    +
+    +Maybe there's a problem with `git version 1.8.4.msysgit.0`.
+    +"""]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_4_b533b1de535a057b7ebf99afc92691ed._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_4_b533b1de535a057b7ebf99afc92691ed._comment
+    new file mode 100644
+    index 0000000..ac4a9e9
+    --- /dev/null
+    +++ b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47/comment_4_b533b1de535a057b7ebf99afc92691ed._comment
+    @@ -0,0 +1,13 @@
+    +[[!comment format=mdwn
+    + username="http://joeyh.name/"
+    + ip="108.236.230.124"
+    + subject="comment 4"
+    + date="2013-10-17T21:49:10Z"
+    + content="""
+    +So this is a problem with msysgit 1.8.4. I have been able to reproduce it with that version. 1.8.3 did not have the problem.
+    +
+    +Seems to perhaps be due to the cygwin xargs flipping git into cygwin path mode somehow. (How all this works is massively complex and confusing to me.)
+    +All the other calls to git with identical parameters work fine. I can also reproduce the problem using some old git 1.7.x in the cygwin terminal.
+    +
+    +BTW, I noticed in your example that you ran \"git commit -a\". You should **never** do that in a [[direct mode]] repository. Read the direct mode documentation to understand why.
+    +"""]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn
+    deleted file mode 100644
+    index dae654d..0000000
+    --- a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn
+    +++ /dev/null
+    @@ -1,63 +0,0 @@
+    -### What steps will reproduce the problem?
+    -[[!format sh """
+    -C:\Users\Bruno>mkdir annex
+    -
+    -C:\Users\Bruno>cd annex
+    -
+    -C:\Users\Bruno\annex>git init
+    -Initialized empty Git repository in C:/Users/Bruno/annex/.git/
+    -
+    -C:\Users\Bruno\annex>git annex init
+    -init
+    -  Detected a crippled filesystem.
+    -
+    -  Enabling direct mode.
+    -
+    -  Detected a filesystem without fifo support.
+    -
+    -  Disabling ssh connection caching.
+    -ok
+    -(Recording state in git...)
+    -
+    -C:\Users\Bruno\annex>echo test > test
+    -
+    -C:\Users\Bruno\annex>git annex add .
+    -add test (checksum...) ok
+    -(Recording state in git...)
+    -
+    -C:\Users\Bruno\annex>git commit -a -m added
+    -[master (root-commit) 2eea610] added
+    - 1 file changed, 1 insertion(+)
+    - create mode 120000 test
+    -
+    -C:\Users\Bruno\annex>git annex sync
+    -(Recording state in git...)
+    -fatal: unable to access '../../../../C:\Users\Bruno\annex\.git/config': Invalid argument
+    -
+    -git-annex: user error (xargs ["-0","git","--git-dir=C:\\Users\\Bruno\\annex\\.git","--work-tree=C:\\Users\\Bruno\\annex","add","-f"] exited 123)
+    -failed
+    -git-annex: sync: 1 failed
+    -"""]]
+    -
+    -### What version of git-annex are you using? On what operating system?
+    -Windows 8 (64 bits)
+    -
+    -git version 1.8.4.msysgit.0
+    -
+    -[[!format sh """
+    -git-annex version: 4.20131008-ge115441
+    -build flags: Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash
+    -key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
+    -remote types: git gcrypt S3 bup directory rsync web webdav glacier hook
+    -local repository version: 4
+    -default repository version: 3
+    -supported repository versions: 3 4
+    -upgrade supported from repository versions: 2
+    -"""]]
+    -
+    -### Please provide any additional information below.
+    -C:\Users\Bruno\annex\.git\config exists
+    -
+    -> xargs was one problem; also msysgit seems to just not
+    -> accept DOS style paths anymore in --git-dir or --git-work-tree.
+    -> megaweird. [[fixed|done]] --[[Joey]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment
+    deleted file mode 100644
+    index cc616aa..0000000
+    --- a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_1_e6f39b2ef55b0daa491f4b6329a906bc._comment
+    +++ /dev/null
+    @@ -1,8 +0,0 @@
+    -[[!comment format=mdwn
+    - username="http://joeyh.name/"
+    - ip="64.134.31.139"
+    - subject="comment 1"
+    - date="2013-10-16T20:42:07Z"
+    - content="""
+    -I don't know what to make of this bug report. You say that \"C:\Users\Bruno\annex.git\config\" exists, but you show the creation of a \"C:\Users\Bruno\annex\", and not the other repository. I cannot reproduce it, even if I first \"git init --bare annex.git\". 
+    -"""]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment
+    deleted file mode 100644
+    index a40e9cb..0000000
+    --- a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_2_b47d6d188f38a8e4ca5ef5f70afadf6a._comment
+    +++ /dev/null
+    @@ -1,48 +0,0 @@
+    -[[!comment format=mdwn
+    - username="https://www.google.com/accounts/o8/id?id=AItOawkGCmVc5qIJaQQgG82Hc5zzBdAVdhe2JEM"
+    - nickname="Bruno"
+    - subject="comment 2"
+    - date="2013-10-16T22:47:46Z"
+    - content="""
+    -There's no other repo yet. I have the same problem when I try to sync between two repos but I simplified the instructions to reproduce the bug easily.
+    -
+    -Here's the instructions on Debian :
+    -[[!format sh \"\"\"
+    -bruno@debian:~$ mkdir annex
+    -bruno@debian:~$ cd annex
+    -bruno@debian:~/annex$ git init
+    -Initialized empty Dépôt git dans /home/bruno/annex/.git/
+    -bruno@debian:~/annex$ git annex init
+    -init  ok
+    -(Recording state in git...)
+    -bruno@debian:~/annex$ echo test > test
+    -bruno@debian:~/annex$ git annex add .
+    -add test (checksum...) ok
+    -(Recording state in git...)
+    -bruno@debian:~/annex$ git commit -a -m added
+    -[master (root-commit) 631049d] added
+    - 1 file changed, 1 insertion(+)
+    - create mode 120000 test
+    -bruno@debian:~/annex$ git annex sync
+    -commit
+    -ok
+    -bruno@debian:~/annex$\"\"\"]]
+    -
+    -It seems --git-dir wants 'c:/...' instead of 'c:\\...'.
+    -
+    -[[!format sh \"\"\"
+    -C:\Users\Bruno\annex>git --git-dir=C:\\Users\\Bruno\\annex\\.git --work-tree=C:\\Users\\Bruno\\annex add -f test
+    -fatal: unable to access '../../../../C:\\Users\\Bruno\\annex\\.git/config': Invalid argument
+    -
+    -C:\Users\Bruno\annex>git --git-dir=C:/Users/Bruno/annex/.git --work-tree=C:\\Users\\Bruno\\annex add -f test
+    -
+    -C:\Users\Bruno\annex>\"\"\"]]
+    -
+    -It's weird that I don't have any problem with the following command:
+    -[[!format sh \"\"\"C:\Users\Bruno\annex>git --git-dir=C:\\Users\\Bruno\\annex\\.git --work-tree=C:\\Users\\Bruno\\annex config -l
+    -core.symlinks=false
+    -core.autocrlf=true
+    -[...]\"\"\"]]
+    -
+    -Maybe there's a problem with `git version 1.8.4.msysgit.0`.
+    -"""]]
+    diff --git a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_4_b533b1de535a057b7ebf99afc92691ed._comment b/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_4_b533b1de535a057b7ebf99afc92691ed._comment
+    deleted file mode 100644
+    index ac4a9e9..0000000
+    --- a/doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__/comment_4_b533b1de535a057b7ebf99afc92691ed._comment
+    +++ /dev/null
+    @@ -1,13 +0,0 @@
+    -[[!comment format=mdwn
+    - username="http://joeyh.name/"
+    - ip="108.236.230.124"
+    - subject="comment 4"
+    - date="2013-10-17T21:49:10Z"
+    - content="""
+    -So this is a problem with msysgit 1.8.4. I have been able to reproduce it with that version. 1.8.3 did not have the problem.
+    -
+    -Seems to perhaps be due to the cygwin xargs flipping git into cygwin path mode somehow. (How all this works is massively complex and confusing to me.)
+    -All the other calls to git with identical parameters work fine. I can also reproduce the problem using some old git 1.7.x in the cygwin terminal.
+    -
+    -BTW, I noticed in your example that you ran \"git commit -a\". You should **never** do that in a [[direct mode]] repository. Read the direct mode documentation to understand why.
+    -"""]]