Geek asks and answers

In subversive activities, I want to go back to the revision, then go to each revision to see where it broke

My project crashed somewhere in the last 25 versions. I need to isolate the file causing the problem and would like to find the version in which the problem was asked.

I thought to use svn update -r 404, and then each of them after405,406 ... etc

Is there a better way?

+3
source share
3 answers

I would suggest using the git-svn bridge (git is great for fast local branching) and using git bisect to quickly find the fix that broke it.

0
source

I am surprised that people did not mention svn-bisect

$ svn-bisect --min 404 --max 429 start
$ svn-bisect bad
$ svn-bisect bad
$ svn-bisect good
[etc etc]
$ svn-bisect reset
+4

svn-bisect , , :

$svn-bisect run 'command [arg...]'

To speed up the search, I would recommend cloning the svn repository into a local git or hg repository and running a bisector there. Both support bisect automation:

$ hg bisect -c 'cmd ...'

or

$ git bisect run '...'

+1
source

More articles:


All Articles