git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yasushi SHOJI <yashi@atmark-techno.com>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: diff: --quiet does not imply --exit-code if --diff-filter is present
Date: Wed, 01 Jun 2011 18:41:48 +0900	[thread overview]
Message-ID: <87pqmxkhwj.wl@dns1.atmark-techno.com> (raw)
In-Reply-To: <20110531153356.GB2594@sigill.intra.peff.net>

Hi Jeff,

At Tue, 31 May 2011 11:33:56 -0400,
Jeff King wrote:
> 
> On Tue, May 31, 2011 at 07:34:39PM +0900, Yasushi SHOJI wrote:
> 
> > just noticed that quiet does not return exit code when I set
> > diff-filter.  at the current tip (v1.7.5.3-401-gfb674d7):
> > 
> >   git diff --quiet     --diff-filter=A v1.7.5 v1.7.5.1 -- t  #=> 0
> >   git diff --exit-code --diff-filter=A v1.7.5 v1.7.5.1 -- t  #=> 1
> > 
> > these two line returns different exit code.
> > 
> > is this a bug or a feature?
> 
> It's a bug.

your patch works like a charm.  Thanks.

> Commit 2cfe8a6 (diff --quiet: disable optimization when
> --diff-filter=X is used, 2011-03-16) fixes this in some
> cases by disabling the optimization when a filter is
> present. However, it only tweaked run_diff_files, missing
> the similar case in diff_tree. Thus the fix worked only for
> diffing the working tree and index, but not between trees.

oh, sorry about not realizing the commit 2cfe8a6.

regards,
-- 
           yashi

      parent reply	other threads:[~2011-06-01  9:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31 10:34 diff: --quiet does not imply --exit-code if --diff-filter is present Yasushi SHOJI
2011-05-31 15:33 ` Jeff King
2011-05-31 15:46   ` Junio C Hamano
2011-05-31 16:25     ` Jeff King
2011-05-31 17:06       ` Re* " Junio C Hamano
2011-05-31 17:14         ` Jeff King
2011-05-31 17:36           ` Junio C Hamano
2011-06-01  9:41   ` Yasushi SHOJI [this message]

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=87pqmxkhwj.wl@dns1.atmark-techno.com \
    --to=yashi@atmark-techno.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).