>>>>> On 2008-09-01 03:31 PDT, Junio C Hamano writes:
Junio> 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.
Junio> My knee-jerk reaction is that I do not particularly
Junio> like this, but I haven't thought things through. What
Junio> does --exit-code do with or without the configuration
Junio> variable?
git diff --exit-code silently refreshes the index and returns 0,
as documented and as I expect. So I further expect "git diff
--exit-code --quiet" to be have the same semantics as "git diff
--exit-code >/dev/null".
What don't you like about this? Isn't this the point of
diff.autorefreshindex ?
--
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
