Karl Chen <quarl@xxxxxxxxxxxxxxx> writes: > When diff.autorefreshindex is true, if a file has merely been 'touched' > (mtime changed, but contents unchanged), then `git-diff --quiet' will > now return 0 (indicating no change) instead of 1, and also silently > refresh the index. My knee-jerk reaction is that I do not particularly like this, but I haven't thought things through. What does --exit-code do with or without the configuration variable? -- 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