News for hackers. Stuff that matters.
Re:What’s Wrong with Git? A Conceptual Design Analysis by haberman on Monday December 30, 2013 @12:53PM (#6985771)
This doesn't really have anything to do with my point. Even if you later edit commits before pushing them, it is still the case that any partially-staged commit that you do ultimately push will reflect a filesystem state that never existed in your working directory (unless you manually checkout the intermediate commit later as a "detached head" and test that).

Maybe some people don't care that every public commit can actually build and run tests, but any broken intermediate tree will break git-bisect or similar tools.

Re:What’s Wrong with Git? A Conceptual Design Analysis by structural on Monday December 30, 2013 @01:36PM (#6986027)
As a matter of fact, manually checking out all the intermediate commits and building/testing those is precisely what our team does.

Except, it's not done manually, we have a set of tools that walks along a branch and tries to build each revision, storing the build/test status using the commit's SHA-1 hash as a key so that we don't waste effort rebuilding things unnecessarily. Then, this is used for our code reviews to verify that each commit on the branch to be integrated has a clean build/test status saved -- or an explanation why not.

We've given some thought into writing a version of git bisect that takes this cached data as input to select better trees to try given some set of known broken commits, but that hasn't happened quite yet.