From: Jeff King <peff@peff.net>
To: Tim Henigan <tim.henigan@gmail.com>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] diff: exit(1) if 'diff --quiet <repo file> <external file>' finds changes
Date: Fri, 15 Jun 2012 14:40:30 -0400 [thread overview]
Message-ID: <20120615184030.GC14843@sigill.intra.peff.net> (raw)
In-Reply-To: <1339781463-13536-1-git-send-email-tim.henigan@gmail.com>
On Fri, Jun 15, 2012 at 01:31:03PM -0400, Tim Henigan wrote:
> When running 'git diff --quiet <file1> <file2>', if file1 or file2
> is outside the repository, it will exit(0) even if the files differ.
> It should exit(1) when they differ.
>From your description, I would expect the fix to be in builtin/diff.c,
or in diff-no-index.c, since that is where the code paths diverge.
> This was the least invasive fix that I found. I considered adding
> the following when the '--quiet' option is parsed instead:
>
> + DIFF_OPT_SET(options, EXIT_WITH_STATUS)
> + DIFF_OPT_SET(options, DIFF_FROM_CONTENTS)
We already set EXIT_WITH_STATUS when we see --quiet (we just do it a
little later, during diff_setup_done). We would not want to set
DIFF_FROM_CONTENTS all the time with --quiet. The point of that flag is
"we cannot know just from seeing the path sha1s whether they are
different or not, because we are doing content-level munging" (for
example, things like ignoring whitespace changes).
So we would not want to always set it whenever --quiet is given, because
it means we must do a lot of extra work comparing file content.
> diff --git a/diff.c b/diff.c
> index 77edd50..b1d74fe 100644
> --- a/diff.c
> +++ b/diff.c
> @@ -4432,9 +4432,10 @@ void diff_flush(struct diff_options *options)
> separator++;
> }
>
> - if (output_format & DIFF_FORMAT_NO_OUTPUT &&
> + if ((output_format & DIFF_FORMAT_NO_OUTPUT &&
> DIFF_OPT_TST(options, EXIT_WITH_STATUS) &&
> - DIFF_OPT_TST(options, DIFF_FROM_CONTENTS)) {
> + DIFF_OPT_TST(options, DIFF_FROM_CONTENTS)) ||
> + DIFF_OPT_TST(options, QUICK)) {
> /*
> * run diff_flush_patch for the exit status. setting
> * options->file to /dev/null should be safe, becaue we
And this is equally bad, because it means that --quiet gets much slower
for _all_ cases, not just the no-index case.
I suspect what you actually want is to set DIFF_FROM_CONTENTS in the
no-index case, since we by definition do not have a pair of sha1s to
compare. But it may also be that diff.c could detect this case
automatically. I'd have to look closer.
-Peff
next prev parent reply other threads:[~2012-06-15 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-15 17:31 [PATCH] diff: exit(1) if 'diff --quiet <repo file> <external file>' finds changes Tim Henigan
2012-06-15 18:40 ` Jeff King [this message]
2012-06-15 19:13 ` Jeff King
2012-06-15 18:45 ` Junio C Hamano
2012-06-15 19:37 ` Jeff King
2012-06-15 19:56 ` Tim Henigan
2012-06-15 20:08 ` Junio C Hamano
2012-06-15 20:24 ` Jeff King
2012-06-15 20:44 ` Junio C Hamano
2012-06-15 20:10 ` Junio C Hamano
2012-06-18 17:51 ` Tim Henigan
2012-06-18 18:00 ` 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=20120615184030.GC14843@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=tim.henigan@gmail.com \
/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).