I tried to use git bisect lately, but it just didn't work. The tree remained in master and I saw no output from git bisect whatsoever. Here's what I've tried: git bisect start git bisect bad # no output, tried a couple of times git bisect good # no output git bisect reset #-> Already on 'master' I tried this on two different repos....
My usual workflow when starting a git bisect session is: git bisect start # start a bisect session git bisect bad # I noticed that the current state is broken Now, often I know that things worked in the past, but I don't know yet which version was good, so I usually want to revert my working tree to an older state,...
The git-bisect provides hooks to perform a binary search on revisions and figure out which change broke the design. Is there an equivalent script for Perforce? I did SO and Google searches with no luck. Update Mar 1 2010: As Douglas Leeder correctly pointed out, this is easy with a linear history. However we do have multiple branches...
I tend 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? Converting the svn repository to git is not an option because it is a fairly large one and the svn server is dog slow - the conversion would take days. ...
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 tests). I'd like to make git bisect automatically skip commits which affect files in certain directories. Is this possible somehow? ...
In some cases during a git bisect session, testing a particular commit takes quite long (for instance, because I have to build a full release package and deploy it on a particularly strange machine). In fact, testing a build takes so long that I'd like to start building the next two commits already without knowing whether the current tes...