Added a comment
authoryarikoptic <yarikoptic@web>
Thu, 16 Feb 2017 15:54:18 +0000 (15:54 +0000)
committeradmin <admin@branchable.com>
Thu, 16 Feb 2017 15:54:18 +0000 (15:54 +0000)
doc/todo/output_of_wanted___40__and_possibly_group_etc__41___should_not_be_polluted_with___34__informational__34___messages/comment_2_c43e838b750448fe4d1519e72c43242f._comment [new file with mode: 0644]

diff --git a/doc/todo/output_of_wanted___40__and_possibly_group_etc__41___should_not_be_polluted_with___34__informational__34___messages/comment_2_c43e838b750448fe4d1519e72c43242f._comment b/doc/todo/output_of_wanted___40__and_possibly_group_etc__41___should_not_be_polluted_with___34__informational__34___messages/comment_2_c43e838b750448fe4d1519e72c43242f._comment
new file mode 100644 (file)
index 0000000..dbd8edb
--- /dev/null
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="yarikoptic"
+ avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
+ subject="comment 2"
+ date="2017-02-16T15:54:18Z"
+ content="""
+Thank you CandyAngel for the feedback.  I do know how to avoid it, but my point is that git-annex here uses stdout for both \"log messages\" and the output of the log command. IIRC some other commands, and git uses stderr for log/informational messages in cases where stdout is used for communicating output
+"""]]