From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [PATCH 0/2] Update "diff -w --exit-code"
Date: Sat, 23 May 2009 12:24:48 -0700 [thread overview]
Message-ID: <1243106690-6385-1-git-send-email-gitster@pobox.com> (raw)
Here is a re-roll of the earlier patch to change the exit status of "diff"
family of commands on whitespace only changes.
Earlier, "-w" and friends only affected the displayed of textual diff
output and never caused the commands to ignore the presense of
differences. With this, the commands exit with zero status when the
changes are only about whitespaces that you are ignoring.
E.g. starting from a clean slate:
$ echo ' a' >a-file ;# one space
$ git add a-file
$ echo ' a' >a-file ;# two spaces
$ git diff --exit-code -w >/dev/null; echo $?
will give 0, instead of 1.
The fact that you have changes (i.e. the contents of a-file as a whole has
changed) is still reported in the textual part of the output by showing
the "diff --git a/a-file b/b-file" header and the "index objname..objname mode"
line. This is not likely to change.
Junio C Hamano (2):
diff: change semantics of "ignore whitespace" options
diff: Rename QUIET internal option to QUICK
builtin-log.c | 2 +-
builtin-rev-list.c | 2 +-
diff-lib.c | 4 +-
diff.c | 39 ++++++++++++++++++++++---
diff.h | 3 +-
revision.c | 2 +-
t/t4037-whitespace-status.sh | 63 ++++++++++++++++++++++++++++++++++++++++++
tree-diff.c | 3 +-
8 files changed, 106 insertions(+), 12 deletions(-)
create mode 100755 t/t4037-whitespace-status.sh
next reply other threads:[~2009-05-23 19:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-23 19:24 Junio C Hamano [this message]
2009-05-23 19:24 ` [PATCH 1/2] diff: change semantics of "ignore whitespace" options Junio C Hamano
2009-05-23 19:24 ` [PATCH 2/2] diff: Rename QUIET internal option to QUICK Junio C Hamano
2009-05-25 11:04 ` [PATCH 1/2] diff: change semantics of "ignore whitespace" options Jeff King
2009-05-25 18:48 ` Junio C Hamano
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=1243106690-6385-1-git-send-email-gitster@pobox.com \
--to=gitster@pobox.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 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 NNTP newsgroup(s).