aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@kodama.kitenet.net>2008-07-19 13:36:06 -0400
committerJoey Hess <joey@kodama.kitenet.net>2008-07-19 13:36:06 -0400
commitfcfbf252e2abc99b06c489aa993652d42a0c2f3f (patch)
tree0b8ca009f814ba122582f175410437646534cc45
parentcc2c8ac8bba85c18a1dc3f57a55b04f263da990f (diff)
downloadikiwiki-fcfbf252e2abc99b06c489aa993652d42a0c2f3f.tar
ikiwiki-fcfbf252e2abc99b06c489aa993652d42a0c2f3f.tar.gz
respinse
-rw-r--r--doc/bugs/git_stderr_output_causes_problems.mdwn6
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/bugs/git_stderr_output_causes_problems.mdwn b/doc/bugs/git_stderr_output_causes_problems.mdwn
index e86b7842f..884f31154 100644
--- a/doc/bugs/git_stderr_output_causes_problems.mdwn
+++ b/doc/bugs/git_stderr_output_causes_problems.mdwn
@@ -31,3 +31,9 @@ Ikiwiki's git handling is sending a bunch of output to stderr. The following pa
>
> (Also indented all the lines of your patch so markdown won't eat it :-) )
> --[[smcv]]
+
+> Right, I don't like throwing stderr away because stderr is supposed to be
+> logged to error.log for a reason: To allow debugging problems.
+> It's unfortunate that git [abuses atderr](http://bugs.debian.org/447395),
+> outputting non-errors to it. That doesn't mean that git might not also
+> output actual error messages there. --[[Joey]]