• cvs2svn Command Line Help

    Syntax

    cvs2svn [-a svn-repos-path | --dumpfile=PATH] cvs-repos-path

    or   (when using an options file use the syntax below)                   
    

    cvs2svn --options=PATH

     

    Switches (switches that can be used with the options file are in italics, the full list can be used with the other syntax)

    --help | -h		Print the usage message and exit with success          
    
    --help-passes		Print the numbers and names of the conversion passes and exit with success          
    
    --version		Print the version number          
    
    --verbose | -v		Tell cvs2svn to print lots of information about what it is doing to STDOUT           
    
    --quiet | -q		Tell cvs2svn to operate in quiet mode, printing little more than pass starts and       
    
    			stops to STDOUT. This option may be specified twice to suppress all non-error output        
    
    --s PATH		Load CVS repository into the Subversion repository located at PATH. If there is no       
    
    			Subversion repository at PATH create a new one.                   
    
    -p PASS			Execute only pass PASS of the conversion. PASS can be specified by name or by number       
    
    			(see --help-passes)       
    
    -p [START]:[END]	Execute passes START through END of the conversion (inclusive). START and END can be       
    
    			specified by name or by number (see --help-passes). If START or END is missing, it       
    
    			defaults to the first or last pass, respectively       
    
    
    --existing-svnrepos	Load the converted CVS repository into an existing Subversion repository, instead of       
    
    			creating a new one       
    
    --dumpfile=PATH		Output the converted CVS repository into a Subversion dumpfile instead of a Subversion       
    
    			repository (useful for importing a CVS repository into an existing Subversion repository.       
    
    
    			PATH is the filename in which to store the dumpfile       
    
    --dry-run		Do not create a repository or a dumpfile, just print the details of what cvs2svn would do if       
    
    			it were really converting your repository.          
    
    --use-cvs		If RCS co is having trouble extracting certain revisions, you may need to pass this flag which       
    
    			causes cvs2svn to use CVS instead of RCS to read the repository. RCS is much faster, so it is       
    
    			the default,but in certain rare cases it has problems with data that CVS does not have        
    
    			problems with. Specifically:       
    
    
    			*  RCS can't handle spaces in author names           
    
          			*  "Unterminated keyword" misread by RCS           
    
          			*  RCS handles the "$Log$" keyword differently from CVS          
    
    
    --trunk-only		Convert only the main line of development from the CVS repository (commonly       
    
    			referred to in Subversion parlance as "trunk"), ignoring all tags and branches        
    
    --trunk=PATH		The top-level path to use for trunk in the Subversion repository. The default       
    
    			value is "trunk"       
    
    --branches=PATH		The top-level path to use for branches in the Subversion repository. The default       
    
    			value is "branches"       
    
    --tags=PATH		The top-level path to use for tags in the Subversion repository. The default       
    
    			value is "tags"       
    
    --no-prune		When all files are deleted from a directory in the Subversion repository, don't       
    
    			delete the empty directory (the default is to delete any empty directories)       
    
    --encoding=ENC		Use ENC as the encoding for filenames, log messages, and author names in the CVS       
    
    			repos. This option may be specified multiple times, in which case the encodings       
    
    			are tried in order until one succeeds. Default: ascii       
    
    
    --fallback-encoding=ENC  If all of the encodings specified with --encoding fail, then fall back to using       
    
    			 ENC in local 'replace' mode. Use of this option may cause information to be lost,       
    
    			 but at least it allows the conversion to run to completion. Default: disabled         
    
    
    --force-branch=REGEXP	Force symbols whose names match REGEXP (a regular expression) to be branches          
    
    --force-tag=REGEXP	Force symbols whose names match REGEXP to be tags. This will cause an error if such a       
    
    			symbol has commits on it         
    
    --exclude=REGEXP	Exclude branches and tags whose names match REGEXP from the conversion.          
    
    
    --symbol-default=OPT	Specify how to convert ambiguous symbols (i.e., those that appear in the CVS archives for       
    
    			both branches and tags). OPT is one of the following:         
    
    			*  "branch": Treat every ambiguous symbol as a branch           
    
         			*  "tag": Treat every ambiguous symbol as a tag           
    
          			*  "heuristic": Decide how to treat each ambiguous symbol based on whether it was used more       
    
    			   often as a branch or tag in CVS.         
    
          			*  "strict": No default; every ambiguous symbol has to be resolved manually using       
    
    			   --force-branch, --force-tag, or --exclude. (This is the default behavior.)         
    
    --no-cross-branch-commits  Prevent the creation of SVN commits that affect multiple branches or trunk and a branch.       
    
    			   Instead, break such changesets into multiple commits, one per branch.         
    
    
    --symbol-transform=PAT:SUB  Transform RCS/CVS symbol names before entering them into Subversion. PAT is a Python        
    
    			    regexp pattern and SUB is a replacement pattern using Python's reference syntax. You may        
    
    			    specify any number of these options; They will be applied in the order given on the        
    
    			    command line. This option can be useful if you're converting a repository in which the        
    
    			    developer uses directory-wide symbol names like 1_0, 1_1 and 2_0 as a kludgy form of         
    
    			    release tagging (the C-x v s command in Emacs VC mode encourages this practice).          
    
    				A command like:  cvs2svn --symbol-transform=' ([0-9])-(.*):release-\1.\2' -q -s SVN                   
    
    			    will transform a local CVS repository into a local Subversion repository, performing the        
    
    			    following sort of mappings          
    
     			    of RCS symbolic names to Subversion tags:                   
    
    				1_0 -> release-1.0           
    
    
      				1_1 -> release-1.1           
    
      				2_0 -> release-2.0                   
    
    
    --username=NAME		Use NAME as the author for cvs2svn-synthesized commits (the default value is no author at all).          
    
    --fs-type=TYPE		Pass the --fs-type=TYPE option to "svnadmin create" when creating a new repository          
    
    --bdb-txn-nosync	Pass the -bdb-txn-nosync switch to "svnadmin create" when creating a new repository          
    
    --cvs-revnum		Record CVS revision numbers as file properties in the Subversion repository. (note that unless        
    
    			it is removed explicitly, the last CVS revision number will remain associated with the        
    
    			file even after the file is changed within Subversion          
    
    --mime-types=FILE	Specify an apache-style mime.types file for setting svn:mime-type properties on files in the        
    
    			Subversion repository.          
    
    --auto-props=FILE	Specify a file in the format of Subversion's config file, whose [auto-props] section can be         
    
    			used to set arbitrary properties on files in the Subversion repository based on their         
    
    			filenames. (the [auto-props] section header must be present; other sections of the config file,         
    
    			including the enable-auto-props setting, are ignored.) Filenames are matched to the filename        
    
    			 patterns case-sensitively unless the --autoprops-ignore-case option is specified.          
    
    --eol-from-mime-type	For files that don't have the kb expansion mode but have a known mime type, set their style
    
    			based on the mime type. For such files, set the svn:eol-style property to "native" if the
    
     			mime type begins with "text/", and leave it unset (i.e., no EOL translation) otherwise. Files         
    
    			with unknown mime types are not affected by this option. This option has no effect unless the
    
    		    	--mime-types option is also specified     
    
    --no-default-eol	Files that don't have the kb expansion mode and (if --eol-from-mime-type is set) unknown         
    
    			mime type usually have their svn:eol-style property set to "native" If this option is         
    
    			specified, such files are left with no eol-style (i.e., no EOL translations)         
    
    --keywords-off		By default, cvs2svn sets svn:keywords on CVS files to "author id date" if the mode of the         
    
    			RCS file in question is either kv, kvi or NOT kb. If you use the --keywords-off switch,          
    
    			cvs2svn will not set svn:keywords for any file. While this will not touch the keywords in         
    
    			the contents of your files, Subversion will not expand them          
    
    --tmpdir=PATH		Use the directory PATH for all of cvs2svn's temporary data (which can be a lot of data).         
    
    			The default value is the current working directory         
    
    --skip-cleanup		Prevent the deletion of the temporary files that cvs2svn creates in the process of conversion          
    
    --profile		Dump Python Hotshot profiling data to the file cvs2svn.hotshot          
    
    --svnadmin=PATH		If the svnadmin program is not in your $PATH you should specify its absolute path with this 
    			
    			switch          
    
    --co=PATH		If the co program (a part of RCS) is not in your $PATH you should specify its absolute path          
    
    			with this switch. (co is needed if --use-cvs is not specified.)         
    
    --cvs=PATH		If the cvs program is not in your $PATH you should specify its absolute path with this switch.          
    
     			(CVS is needed if --use-cvs is specified)          
    
    --sort=PATH		If the GNU sort program is not in your $PATH you should specify its absolute path with this           
    
     			switch cvs2svn requires GNU sort; Windows sort.exe is not adequate