git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Documentation/git-diff: remove -r from --name-status example
Date: Sun, 29 Jul 2007 13:24:20 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707291323150.14781@racer.site> (raw)
In-Reply-To: <20070729121948.GA21983@coredump.intra.peff.net>

Hi,

On Sun, 29 Jul 2007, Jeff King wrote:

> On Sun, Jul 29, 2007 at 01:04:13PM +0100, Johannes Schindelin wrote:
> 
> > The idea is this: when "--quiet" was given, we do not output anything, and 
> > therefore do not have to recurse into the directories, because we already 
> > know that there are differences when a _tree_ is different.  I do not 
> > remember all details of the "--quiet" implementation, but I think that it
> > 
> > - exits early (as you said)
> > 
> > - does not turn on "recursive" to avoid unnecessary work.
> 
> OK, looking through the code, this works _sometimes_. If I say "git-diff
> --quiet" then it will not recurse. If I say "git-diff -p --quiet" then
> it will (even though we never show the -p output).

That is expected behaviour.  If you ask for it, it should be done (however 
silly it might be).

> Since --quiet supersedes all output formats, I think it probably should 
> just clear the recursive option entirely. In which case rather than 
> special-casing quiet to avoid recursion in git-diff, we can simply turn 
> on recursion before parsing options (and it will get turned off 
> correctly by any diff options that need to do so).

No.  Just think about "git diff -p -w --quiet".  In some cases it _has_ to 
recurse.

Ciao,
Dscho

  reply	other threads:[~2007-07-29 12:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-29  0:24 [PATCH] Documentation/git-diff: remove -r from --name-status example Jeff King
2007-07-29  2:06 ` Linus Torvalds
2007-07-29  4:11   ` Jeff King
2007-07-29  4:27     ` Linus Torvalds
2007-07-29  4:48       ` Junio C Hamano
2007-07-29  4:56         ` Jeff King
2007-07-29  8:23         ` David Kastrup
2007-07-29  9:36         ` Junio C Hamano
2007-07-29  9:49           ` Jeff King
2007-07-29 11:14             ` Johannes Schindelin
2007-07-29 11:33               ` David Kastrup
2007-07-29 11:38               ` Jeff King
2007-07-29 12:04                 ` Johannes Schindelin
2007-07-29 12:19                   ` Jeff King
2007-07-29 12:24                     ` Johannes Schindelin [this message]
2007-07-29 12:26                       ` Jeff King
2007-07-29 16:51         ` Linus Torvalds
2007-07-29  4:52       ` Jeff King

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=Pine.LNX.4.64.0707291323150.14781@racer.site \
    --to=johannes.schindelin@gmx.de \
    --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).