git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
	"Michael S. Tsirkin" <mst@dev.mellanox.co.il>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH] diff: resurrect the traditional empty "diff --git" behaviour
Date: Fri, 31 Aug 2007 23:32:37 +0200	[thread overview]
Message-ID: <20070831213237.GA4753@steel.home> (raw)
In-Reply-To: <7vtzqfzcll.fsf_-_@gitster.siamese.dyndns.org>

Junio C Hamano, Fri, Aug 31, 2007 22:13:42 +0200:
> The "Consier running git-status" warning message we experimented
> during the 1.5.3 cycle turns out to be a bad idea.  It robbed
> cache-dirty information from people who valued it, while still
> asking users to run "update-index --refresh".  It was hoped that
> the new behaviour would at least have some educational value,
> but not showing the cache-dirty paths like before means the user
> would not even know easily which paths are cache-dirty.
> 
> This commit reinstates the traditional behaviour as the default,
> but with a twist.
> 
> If you set diff.autorefreshindex configuration variable, it
> squelches the empty "diff --git" output, and at the end of the
> command, it automatically runs "update-index --refresh" without
> even bothering the user.  In other words, with the configuration
> variable set, people who do not care about the cache-dirtyness
> do not even have to see the warning.

I like this change.

So far my attempts to explain that warning to myself always left an
uneasy feeling of me having tricked myself into believing in its
usefullness.

  parent reply	other threads:[~2007-08-31 21:33 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-30  6:38 parallel make problem with git Michael S. Tsirkin
2007-08-30  6:46 ` Junio C Hamano
2007-08-30  6:50   ` Michael S. Tsirkin
2007-08-30  7:27   ` [PATCH] fix parallel make problem Michael S. Tsirkin
2007-08-31  2:02     ` Junio C Hamano
2007-08-31  8:06       ` Michael S. Tsirkin
2007-08-31  8:12         ` Junio C Hamano
2007-08-31  8:15           ` Michael S. Tsirkin
2007-08-31  8:36             ` Junio C Hamano
2007-08-31 15:21               ` Michael S. Tsirkin
2007-08-31 15:44                 ` Junio C Hamano
2007-08-31 16:00                   ` Michael S. Tsirkin
2007-08-31 16:11                     ` Johannes Schindelin
2007-08-31 16:01                   ` Junio C Hamano
2007-08-31 16:03                   ` Jeff King
2007-08-31 20:13                     ` [PATCH] diff: resurrect the traditional empty "diff --git" behaviour Junio C Hamano
2007-08-31 20:32                       ` Jeff King
2007-08-31 20:57                         ` Johannes Schindelin
2007-08-31 21:16                           ` Junio C Hamano
2007-08-31 21:30                             ` Johannes Schindelin
2007-08-31 21:20                           ` David Kastrup
2007-08-31 21:32                       ` Alex Riesen [this message]
2007-08-31 22:37                       ` Steven Grimm
2007-09-01  1:27                         ` Junio C Hamano
2007-09-03  8:09                           ` Matthieu Moy
2007-09-03  8:36                             ` 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=20070831213237.GA4753@steel.home \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mst@dev.mellanox.co.il \
    --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).