Matthieu Moy <Matthieu.Moy@xxxxxxx> writes: > 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?): You said it yourself below --- run git-status (or update-index --refresh) first. > I've hit this while working on a project, doing a lot of modifications > through scripting (some regexp substitutions and such kinds of > things). I have to say that you are quite mistaken. Scripted style bulk modification that indiscriminately touch everbody but actually only modifies some, e.g. "perl -p -i", is a fine component of people's workflow, but that is *NOT* the norm. If it were, then you are not programming nor editing -- your script is doing the work. But as you know, after such a bulk operation, you can always... > ... until I run git-status again. ... refresh away the cache-dirtiness. The default should be tuned for users who perform manual editing with status checks. And power users like yourself who run "bulk touch indiscriminately but modify only some" scripts should learn to run git-status (or "update-index --refresh") after such operation. Swapping the defaults to optimize for the abnormal case is madness. - 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
