# svn_load_dirs(1) - man - phpman

[SVN_LOAD_DIRS(1)](https://www.chedong.com/phpMan.php/man/SVNLOADDIRS/1/markdown)                       General Commands Manual                      [SVN_LOAD_DIRS(1)](https://www.chedong.com/phpMan.php/man/SVNLOADDIRS/1/markdown)



## NAME
       svn_load_dirs - Load directories into a Subversion repository


## SYNOPSIS
       **svn**___**load**___**dirs** [_options_] _svn_url_ _svn_import_dir_ [_directory_ ...]


## DESCRIPTION
       This tool can be used for importing one or more directories into a Subversion repository. The
       difference from "svn import" is that svn_load_dirs can update an existing directory tree, and
       tag  it properly. Only changes from the previous version will be recorded in the revision, so
       that you can easily apply them on another branch.  For example, this is very useful for  man‐
       aging the upstream source when maintaining Debian packages in Subversion.


## OPTIONS
       _svn_url_
              The base Subversion URL.

       _svn_import_dir_
              The path relative to _svn_url_ where the directories are to be imported.

       _directory_ _..._
              The  directories  to  import.  If they are not specified on the command line, they are
              read from standard input.

### -no
              Don't ask any questions. Assume that the answer is yes.

### -p
              Apply the properties specified in the configuration file _filename_ to  matching  files.
              See below for a description of the configuration file format.

### -svn
              Username to use when committing to the repository.

### -svn
              Password to use when committing to the repository.

### -t
              Create  a  tag copy in _tag_dir_, relative to _svn_url_. _tag_dir_ may contain a regular ex‐
              pression enclosed within '@' characters. It will be replaced by the matching part from
              the imported directory names.

### -v

### -wc
              Use the already checked out working copy at _path_ instead of checking out a new working
              copy.


## PROPERTY CONFIGURATION FILE FORMAT
       The property configuration file, which is specified by the -p option, contains rules for  ap‐
       plying properties to the imported files.  It consists of lines of the following format:

       _regular_expression_  _control_   _property_name_  _property_value_

       The meaning of the fields are:

       _regular_expression_
              A Perl-style regular expression matching the files to apply this rule to.

       _control_
              Either  "break" or "cont". If set to "break", processing of the current file will stop
              if this rule matches. If set to "cont", processing will continue. The  latter  can  be
              used to set multiple properties for one file.

       _property_name_
              (Optional) The name of the property to set.

       _property_value_
              (Optional) Set the property to this value.

       The  last two fields may be omitted, in which case the rule will not set any properties. This
       is useful for excluding certain files from subsequent rules.

       You need to quote the _regular_expression_, _property_name_ and _property_value_ fields with double
       quotes  ('"')  if  you  have whitespace in them. Single and double quotes can be escaped with
       backslash ('\').


## EXAMPLES
       For example, to import the contents of the foo-1.3 directory into the upstream/current direc‐
       tory of the foo repository:

       svn_load_dirs svn+ssh://svn.example.org/svn/foo upstream/current foo-1.3

       A tag can also be added automatically using the -t option:

       svn_load_dirs  svn+ssh://svn.example.org/svn/foo  -t  'upstream/@\d+\.\w+@'  upstream/current
              foo-1.3

       Here's an example of a property configuration file:

       \.doc$              break     svn:mime-type  application/msword
       \.ds(p|w)$          break     svn:eol-style  CRLF
       \.dos2unix-eol\.sh$ break
       .*                  break     svn:eol-style  native

       This example specifies that .doc files are to be treated as binary files, that .dsp and  .dsw
       files have their line ending characters kept, and that all other files except dos2unix-eol.sh
       have their line endings converted to the native style.


## SEE ALSO
       /usr/share/doc/subversion-tools/svn_load_dirs.README.gz

       [**svn**(1)](https://www.chedong.com/phpMan.php/man/svn/1/markdown)


## AUTHOR
       This manual page was written by Per Olofsson <<pelle@dsv.su.se>> for  the  Debian  distribution
       (but may be used by others). Some parts were taken from the README.



                                                                                    [SVN_LOAD_DIRS(1)](https://www.chedong.com/phpMan.php/man/SVNLOADDIRS/1/markdown)