App-SVN-Bisect
view release on metacpan or search on metacpan
bin/svn-bisect view on Meta::CPAN
=head1 EXAMPLE
...Because, you know, no software documentation is complete without a flashy
screenshot, these days.
So, lets say you were wondering when the subversion project added the
"Last Changed Rev:" line to the output of "svn info". Determining the
existence of this change is a straightforward matter of searching for the
text string... if a result was found, the current revision is "after",
otherwise it was "before". So a bisect looks like this:
$ svn co http://svn.apache.org/repos/asf/subversion/trunk/subversion
[snip lots of subversion checkout spam]
Checked out revision 980012.
$ cd subversion
$ ack --nocolor --nogroup 'Last Changed Rev'
svn/info-cmd.c:362: SVN_ERR(svn_cmdline_printf(pool, _("Last Changed Rev: %ld\n"),
tests/cmdline/depth_tests.py:2056: 'Last Changed Rev' : '^1$',
lib/App/SVN/Bisect.pm view on Meta::CPAN
125: This revision is untestable and should be skipped
any other value: The command failed to run, abort bisection.
The normal caveats apply. In particular, if your script makes any
changes, don't forget to clean up afterwards.
END
'view' => <<"END",
Usage: $0 view
Outputs some descriptive information about where we're at, and about
the revisions remaining to be tested. The output looks like:
There are currently 7 revisions under scrutiny.
The last known-unaffected rev is 28913.
The first known- affected rev is 28928.
Currently testing 28924.
Revision chart:
28913] 28914 28918 28921 28924 28925 28926 28927 [28928
END
( run in 0.392 second using v1.01-cache-2.11-cpan-64827b87656 )