On Wed, Jul 22, 2015 at 10:32 PM, Junio C Hamano <gits...@pobox.com> wrote:
>> "--quite" is documented to "Disable all output of the program". Yet
>> calling diff-tree with a single commit like
>>
>> $ git diff-tree --quiet c925fe2
>>
>> was logging
>>
>> c925fe23684455735c3bb1903803643a24a58d8f
>
> At this point, unfortunately I think we need to call that a
> documentation bug. The "output" it refers to is output from the
> "diff" portion, not the "poor-man's log" portion, of the program,
> where diff-tree was the workhorse behind scripted "git log" that
> gave the commit object name as the preamble for each commit it
> shows information about.
Well, from a user's perspective it does not matter which part of the
internal implementation of diff-tree is responsible for printing that
single line, a user would just expect "--quiet" to really mean
"quiet". As for almost any bug, we could turn it into a feature by
"fixing" the docs and claiming it's documented behavior. To me the
question simply is whether it makes sense for "--quiet" to not be
quiet, and I think it does not make sense. If you run diff-tree this
way there is no added value in the given output.
My use-case (also see [1]) is that I wanted to checked whether some
given commits change nothing but whitespace. So I did
if git diff-tree --quiet --ignore-space-change $commit; then
echo "$commit only changes whitespace."
fi
just to see those SHA1s being printed to the console.
I probably could instead do
if git diff-tree --exit-code --ignore-space-change $commit > /dev/null
2>&1; then
echo "$commit only changes whitespace."
fi
but that defeats the purpose of having "--quiet" in the first place.
[1] http://article.gmane.org/gmane.comp.version-control.git/273975
--
Sebastian Schuberth
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
