All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Schuberth <sschuberth@gmail.com>
To: git@vger.kernel.org
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$1@ger.gmane.org> (raw)

Hi,

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 $?
c925fe23684455735c3bb1903803643a24a58d8f
0

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 $?
c925fe23684455735c3bb1903803643a24a58d8f
1

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to='mo3tel$otc$1@ger.gmane.org' \
    --to=sschuberth@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.