diff options
Diffstat (limited to 'doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment')
| -rw-r--r-- | doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment b/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment deleted file mode 100644 index b7b4d786e..000000000 --- a/doc/bugs/JSON_output_broken_with___34__git_annex_sync__34__/comment_2_282f5f89fb4a46e1fad0980e0b2994a0._comment +++ /dev/null @@ -1,8 +0,0 @@ -[[!comment format=mdwn - username="http://sunny256.sunbase.org/" - nickname="sunny256" - subject="comment 2" - date="2012-11-27T21:30:48Z" - content=""" -Yep, because of that I was in doubt if I should report it as a bug. Maybe it could be closed, as it's not a bug in git-annex, but git output leaking into the JSON. If there's not an easy way for git-annex to encapsulate the output or redirect the git output to stderr. -"""]] |