The authors seem confused by the purpose of the "Assume Unchanged" feature. According to the initial commit [1] it seems intended to be used as a speed optimiza

The authors seem confused by the purpose of the "Assume Unchanged" feature. According to the initial commit [1] it seems intended to be used as a speed optimization for crappy filesystems, and not as some way to avoid committing files with changes. They also say: > Of course, the user might make the set of files explicit on every single commit (leaving out the database configuration file), but this is laborious and error-prone. I find this amusing given that I don't ever use "git add -u" or "git add -A" in my daily git life—"git add -p" is as close as I get (and commit-patch [2] is nice, too). [1] https://github.com/git/git/commit/5f73076c1a9b4b8dc94f77eac98eb558d25e33c0 https://github.com/git/git/commit/5f73076c1a9b4b8dc94f77eac9... [2] http://porkrind.org/commit-patch/ http://porkrind.org/commit-patch/