From: Duy Nguyen Date: Fri, 05 Dec 2014 10:52:15 GMT Subject: Re: bug report on update-index --assume-unchanged Message-ID: In-Reply-To: <548156E5.2080006@kdbg.org> On Fri, Dec 5, 2014 at 1:55 PM, Johannes Sixt 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