mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Sebastian Schuberth <>
Subject: Issues with git diff-tree --quiet --ignore-space-change
Date: Tue, 14 Jul 2015 23:03:14 +0200	[thread overview]
Message-ID: <mo3tel$otc$> (raw)


I believe there's something wrong with diff-tree's --ignore-space-change option in conjunction with --quiet. In Git's repo, I get

$ git --version
git version 2.4.5

$ git diff-tree --quiet --ignore-space-change c925fe23684455735c3bb1903803643a24a58d8f ; echo $?

First question is, why do I see the SHA1 printed to the output, esp. as I specified --quiet?

Secondly, the exit code of 0 indicates there's no diff. However, using

$ git diff-tree --patch --ignore-space-change c925fe23684455735c3bb1903803643a24a58d8f

I see the diff (which does not only consist of whitespaces).

If I omit --ignore-space-change the return value is correct:

$ git diff-tree --quiet c925fe23684455735c3bb1903803643a24a58d8f ; echo $?

Am I missing something, or are these bugs?

Sebastian Schuberth

                 reply	other threads:[~2015-07-14 21:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='mo3tel$otc$' \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).