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

"Shawn O. Pearce" [off-list ref] writes:

quoted

I do not make partial commits myself, so
distinction between staged and unstaged are not something I am
usually interested in.

I never used to either.  Then git-gui got really useful at showing
the distinction and I started using the index for a staging ground.

I guess we are saying the same thing.  I do use index for
staging large-ish changes.  I simply do not care about the
staged/not-staged distinction in the sense that "I still haven't
staged these, that's good because these do not belong to the
commit I am going to make next".

Output from "git diff" being truly empty is the cue that such a
large-ish worktree change is ready to be committed, and the
final "git diff --cached" would give me the full picture.  A
small-ish change won't make "git diff" in the middle empty, but
checking the final "git diff --cached" before committing is the
same.