Thank you for the suggestion, Brice! In this particular case, I had made the change myself (as part of a large refactor), so finding which commit caused the problem was not the issue - it was more a matter of wading through a large pile of changes to find which one had been done incorrectly.
Why don't you use git bisect to try to track what commit introduced the problem?
Thank you for the suggestion, Brice! In this particular case, I had made the change myself (as part of a large refactor), so finding which commit caused the problem was not the issue - it was more a matter of wading through a large pile of changes to find which one had been done incorrectly.
Ok thanks for this precision and thanks for your article.