On Fri, Dec 5, 2014 at 1:55 PM, Johannes Sixt <j...@kdbg.org> wrote: > Actually, it's a user error. When you set --assume-unchanged, then you give > a promise to git that you do not change the files, and git does not have to > check itself whether there is a change. > > But since you did not keep your promise, you get what you deserve. ;-)
You are correct about the original idea behind --assume-unchanged. But over the time I think we bend over a bit and sort of support these use cases. For example, aecda37 (do not overwrite files marked "assume unchanged" - 2010-05-01). The change is one-liner, so I don't mind doing it. -- Duy -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
