Shawn Pearce <spearce@xxxxxxxxxxx> writes: > What may help (and without using assume unchanged) is: > > * skip the `update-index --refresh` part of git-status/git-commit > * skip the status template in COMMIT_MSG when using the editor > > As Git will still at least make sure a `commit -a` includes > everything that is dirty. > > Files whose modification dates may have been messed with (but > whose content are unchanged) will just go through expensive SHA1 > computation to arrive at the same value, which is fine. > > Users skipping the first part are doing so under the assumption that > their modification dates are usually always correct, and that then > they aren't the SHA1 computation of a handful of files is cheap > compared to stat'ing the entire set of files. > > Users skipping the second part are doing so under the assumption > that knowing the names of the files they are committing doesn't > really improve their odds of writing a good commit message. The second part is not about a good commit message but more about a path that should have been updated but forgotten (the same mistake you would be likely to make and that is the reason assume-unchanged is not good for you). I do not mind too much if you added a new --quick option to "git commit" for this rather specialized need. - 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