On Mon, Nov 12, 2018 at 11:22:09PM +0000, brian m. carlson wrote: > This is going to totally hose automation. My last job had files which > might move from tracked to untracked (a file that had become generated), > and long-running CI and build systems would need to be able to check out > one status and switch to the other. Your proposed change will prevent > those systems from working, whereas they previously did. Wouldn't those systems not use -f right now? And shouldn't Git have the same semantic for -f to clobber everything in the proposed use case? Like it does right now for untracked files which are not ignored. So to be save going back and forth I would expect those systems to use -f anyway. Have I missed something here? Regards, Eckhard
