diff options
Diffstat (limited to 'doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment')
| -rw-r--r-- | doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment new file mode 100644 index 000000000..5873167be --- /dev/null +++ b/doc/bugs/whereis_does_not_work_in_direct_mode/comment_5_00926da970a20de67ba7719610f17142._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://svario.it/gioele" + nickname="gioele" + subject="comment 5" + date="2014-08-31T10:15:30Z" + content=""" +I have found out that there is a connection between this problem and the _global_ configuration of `annex.alwayscommit`. This problem will appear only if `annex.alwayscommit` is globally set to `false`. What is very strange is that setting `annex.alwayscommit` locally does not make this bug appear; only a globally set `annex.alwayscommit` will trigger this problem. + +I fixed the test script to set `annex.alwayscommit` globally. + +Now I see why I could reproduce this bug on different machines but Joey could not: all my machines have the same `~/.gitconfig`. +"""]] |