Use 'git bisect' or some similar tool to walk back and find the point where the lock file change triggered the bug?
If you have a lock file, there's no problem. I was arguing about what happens when there isn't a lock file.
I may have inferred something that wasn't in the original comment, by reading too many of the other comments on this page.
Sort but given that we're relying on git mostly, what are the advantages of lock files over submodules/subtrees ?
Well, that would lock all of the projects into git. What if some libraries are in git, and others are in mercurial and darcs?
I think it’s better to have a package manager that’s not reliant on a particular source control system.
And if the new implementation has a new bug, you might be screwed. It worked last week, but not this week. How do I get back to the working version?