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

I find comments like this to be counter productive.
Admin it, git porcelain still has some work to be done.  We can't  
expect new users to know the git internals workflow before they can  
use git effectively.  We can expect new users to read the man pages,  
but not necessarely expect them to understand all the plumbing  
implied by what they read.  Here I think M.Moy understand the  
plumbing and could silently deal with it.  But instead he decided to  
help improve git and decided to raise a flag about inconsistencies he  
faced.  We should never answer request for improvement with ' Just do  
X and be done with it'.  This is a 'geek' answer to a legitime comment.

I know the goal of git is not to reign over the world of vcs, but  
it's not a reason to refuse to improve it when constructive comments  
are made about it.

- jfv

Le 07-08-02 à 06:48, Johannes Schindelin a écrit :

Hi,

On Thu, 2 Aug 2007, Matthieu Moy wrote:

quoted

Johannes Schindelin [off-list ref] writes:

quoted

On Thu, 2 Aug 2007, Matthieu Moy wrote:

quoted

quoted

If the feature still makes sense in the modern world is a
different story, but I do find it useful.

I understand that it can be usefull, but I really don't like  
having it
by default (is there a way to deactivate it BTW?).

Yes.  Just call "git status" and be done with it.

That's not what I mean (my original message mentionned that already
BTW). By "deactivate", I mean "make git-diff never show empty diffs".
I don't want to run two commands where I need only one.

Then don't touch the files you do not want to touch!  Or if you  
want to
have it convenient, and have a script that touches everything, even  
if it
does not change the contents, just add "git add -u" at the end of the
script".  Not that difficult.

Ciao,
Dscho