Re: git-diff on touched files: bug or feature?

From: J. Bruce Fields <bfields@fieldses.org>
Date: Aug 2, 2007, 17:58 UTC
Message-ID: <20070802175838.GA31885@fieldses.org>
In-Reply-To: <vpqtzrivt2n.fsf@bauges.imag.fr>

On Thu, Aug 02, 2007 at 05:45:20PM +0200, Matthieu Moy wrote:

Show 6 quoted lines

> Depending on the kind of things I'm doing, I usually run status
> regularly, because it's short to read, and it shows me both staged and
> unstaged changes.  git-status tells me if I did something obviously
> totally wrong (changing a file on which I was not working, deleting
> something important ...), and after that, git-diff gives me a
> finer-grained vision of what I did.

Yeah, ditto for me. When I return to a project after having been away a few minutes, the first things I do are

	git branch	# remind me which topic I was working on
	git status	# remind me if I was in the middle of something.

So I end up running it a lot. I only do a git-diff if I need some details.

--b.