Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

svn-bisect(1) [debian man page]

SVN-BISECT(1)						      General Commands Manual						     SVN-BISECT(1)

NAME

       svn-bisect - Bisect Subversion revisions to find a regression

SYNOPSIS

       svn-bisect start [good_rev [bad_rev]]

       svn-bisect {good|bad} [rev]

       svn-bisect run command

       svn-bisect reset

       svn-bisect status

DESCRIPTION

       svn-bisect  helps  to  automate	finding a bug or behavior change in a Subversion working copy.	Given an initial "good" revision, with the
       desired or original behavior, and a newer "bad" revision, with the undesired or modified behavior,  svn-bisect  will  do  a  binary  search
       through the revision range to find which revision caused the change.

       svn-bisect  must  be initialized in a working copy, with svn-bisect start.  It also needs to be given at least one good revision (the base-
       line) and one bad revision (known modified behavior) revision.

       Sub-commands:

       start  Initializes or reinitializes svn-bisect; optionally takes good and bad revision parameters.

       good rev

       bad rev
	      Tells svn-bisect that a revision is good or bad, defining or narrowing the search space.	If not specified, revision defaults to the
	      current  revision  in  the working copy.	svn-bisect will then update to a revision halfway between the new good and bad boundaries.
	      If this update crosses a point where a branch was created, it switches in or out of the branch.

       reset  Resets the working copy to the revision and branch where svn-bisect start was run.  In the simple case this is equivalent to  rm	-r
	      .svn-bisect;  svn  update,  but  not  if	it  has crossed branches, and not if you did not start at the HEAD revision.  In any case,
	      svn-bisect never keeps track of mixed-revision working copies, so do not use svn-bisect in a working  copy  that	will  need  to	be
	      restored to mixed revisions.

       status Prints a brief status message.

       run command
	      Runs  the  bisection in a loop.  You must have already defined initial good and bad boundary conditions.	Each iteration through the
	      loop runs command as a shell command (a single argument, quoted if necessary) on the chosen revision, then  marks  the  revision	as
	      good or bad, based on the exit status of command.

EXAMPLES

       Assume you are trying to find which revision between 1250 and 1400 caused the make check command to fail.

	   svn-bisect start 1250 1400
	   svn-bisect run 'make check'
	   svn-bisect reset

ENVIRONMENT

       SVN    The Subversion command-line program to call (default svn).

FILES

       .svn-bisect
	      The directory containing state information, removed after a successful bisection.

SEE ALSO

       git-bisect(1).

AUTHOR

       Written by Robert Millan and Peter Samuelson, for the Debian Project (but may be used by others).

								    2009-10-22							     SVN-BISECT(1)

Check Out this Related Man Page

SVN-ALL-FAST-EXPORT(1)					      General Commands Manual					    SVN-ALL-FAST-EXPORT(1)

NAME

       svn-all-fast-export - tool to convert svn repositories into git

SYNOPSIS

       svn-all-fast-export [options] [Path to subversion repository]

DESCRIPTION

       svn-all-fast-export is a tool to convert your svn repositories to git.

       You  will  need to have a copy of your svn repository and to write some rules to specify how the conversion will be done, for instance, you
       can manage how the tags and branches will be managed writing the appropriate  rules.  You  have	examples  in  /usr/share/doc/svn-all-fast-
       export/samples

       Path  to  subversion  repository is a backup copy of the subversion repository. Note that an svn url will not work due to the undistributed
       nature of svn.

OPTIONS

       --identity-map
	      Provide map between svn username and email. You can provide a file mapping the old svn accounts to the authors names. This file must
	      have a line per each svn account, you can use either the svn-all-fast-export native format:
	      janesvnaccountname Jane Doe <jane.doe@example.com>
	      or the git-svn format:
	      janesvnaccountname = Jane Doe <jane.doe@example.com>

       --revisions-file
	      Provide a file with revisions numbers that should be processed. This file should have one revision number per line.

       --rules
	      The rules file that determines what goes where. See /usr/share/doc/svn-all-fast-export/samples

       --add-metadata
	      If passed, each git commit will have svn commit info.

       --resume-from
	      Start importing at svn revision number.

       --max-rev
	      Stop importing at svn revision number.

       --dry-run
	      Don't actually write anything.

       --debug-rules
	      Print what rule is being used for each file.

       --commit-interval number
	      If passed the cache will be flushed to git every number of commits.

       --stats
	      After a run, print some statistics.

       --svn-branches
	      Use the content of SVN when creating branches, Note: SVN tags are branches as well.

       -h, --help
	      Show summary of options.

       -v, --version
	      Show version of program.

RETURN VALUES

       This program returns 0 on success, on error something else (numbers in base 10):
       10 unrecognized option or missing argument
       11 no rules file specified

BUGS

       All  matching  rules  need  to  end with a '/', else the tool will crash at some point. The only exception are the rules using the recurse-
       action.

HOMEPAGE

       http://gitorious.org/svn2git

SEE ALSO

       http://techbase.kde.org/Projects/MoveToGit/UsingSvn2Git

AUTHORS

       svn-all-fast-export was written by Thiago Macieira and Thomas Zander.

								  April 25, 2010					    SVN-ALL-FAST-EXPORT(1)
Man Page