On Sun, Apr 22, 2018 at 5:23 PM, Andrew Wolfe <andrew@xxxxxxxxxxxxxx> wrote: > Kevin, thanks for your feedback. > > You have a reasonable point, because usually you don't put the outputs of a build into version control, but the build script checks them for being current. > > On the other hand, when you change branches, your existing output directories are worthless problems anyway — even if you have all the interdependencies correct. Because of this, I'm inclined to consider this use case as intrinsically hazardous. When I do a checkout, I always want to purge all the intermediate and end targets regardless. Not every build has this problem, and certainly I think some of the most common build software would not (Make). It's fairly easy to fix this by using a git hook to update files post checkout (you can look up the timestamp of each file's commit time, or any other time and use touch to do this yourself). Thanks, Jake
