On Tue, Oct 02, 2007 at 01:55:16PM -0500, Dan Zwell wrote: > A small personal git repository has started lying to me about changed files. > git-diff sometimes tells me that the index has no changes from HEAD, while > other commands (git-status, at least) seem to tell the truth. It is the same Perhaps you are confused by the fact that "git-diff" with no options shows the difference between the index and the working tree? Did you try "git-diff --cached"? > after I commit the new changes--at that point, "git-diff-tree HEAD^ HEAD -p" > spits out a nice patch, but "git-diff HEAD^ HEAD" gives nothing. That doesn't seem right. Can you reproduce this, or at least show us the command you used? > $ git status > # On branch bak_linear-checks3 > nothing to commit (working directory clean) > $ echo "test" >> Makefile > $ git status > # On branch bak_linear-checks3 > # Changed but not updated: > # (use "git add <file>..." to update what will be committed) > # > # modified: Makefile > # > no changes added to commit (use "git add" and/or "git commit -a") > $ git diff > $ OK, that does seem wrong. If you run git-diff-files, does it produce the expected output? -Peff - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
