I\'m aware that git bisect is branch-aware by design, so that if between good commit, G, and bad commit, B, you merged in a branch, it needs to take those changes开发者_如何学Go into consideration as
I\'m using git bisect to find a failure inducing commit. However, a lot of the commits in the range are definately irrelevant (because they开发者_如何学运维 are commits to the documentation or to unit
I te开发者_开发问答nd to use the bisect command in git extensively. Now I want to do the same in a subversion repository. What is the best way to bisect a subversion repository?
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
I tried to use git bisect lately, but it just didn\'t work. The tree remained in master and I saw no outp开发者_如何学JAVAut from git bisect whatsoever. Here\'s what I\'ve tried: