summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorGravatar benjamin.poldrack@d09ccff6d42dd20277610b59867cf7462927b8e3 <benjaminpoldrack@web>2017-02-22 16:48:04 +0000
committerGravatar admin <admin@branchable.com>2017-02-22 16:48:04 +0000
commit7c4586f8bb0bca64449966bbd6205951f193fede (patch)
treea8d4cb07a8b35a01067aef82ad803291792c4934 /doc
parent5cb52e7b6171ffc82fd827270fde42e82014dcd5 (diff)
Added a comment
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/git_annex_status_fails_with_submodule_in_direct_mode/comment_5_e7c09850009e961354e26f169ccdc6e3._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/git_annex_status_fails_with_submodule_in_direct_mode/comment_5_e7c09850009e961354e26f169ccdc6e3._comment b/doc/bugs/git_annex_status_fails_with_submodule_in_direct_mode/comment_5_e7c09850009e961354e26f169ccdc6e3._comment
new file mode 100644
index 000000000..a2af5ca08
--- /dev/null
+++ b/doc/bugs/git_annex_status_fails_with_submodule_in_direct_mode/comment_5_e7c09850009e961354e26f169ccdc6e3._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="benjamin.poldrack@d09ccff6d42dd20277610b59867cf7462927b8e3"
+ nickname="benjamin.poldrack"
+ avatar="http://cdn.libravatar.org/avatar/5c1a901caa7c2cfeeb7e17e786c5230d"
+ subject="comment 5"
+ date="2017-02-22T16:48:04Z"
+ content="""
+Just noticed another thing: If that failure happens, git-annex exits zero. Therefore it's hard to detect for us. We have just an empty json as return value as if the repo was clean.
+It would be nice to have either a non-zero exit or something within the json to indicate that the command failed.
+
+[[ben]]
+"""]]