• Name

    svn export – Export a clean directory tree.

    Synopsis

    svn export [-r REV] URL[@PEGREV] [PATH]
    svn export [-r REV] PATH1[@PEGREV] [PATH2]

    Description

    The first form exports a clean directory tree from the repository specified by URL, at revision REV if it is given, otherwise at HEAD, into PATH. If PATH is omitted, the last component of the URL is used for the local directory name.

    The second form exports a clean directory tree from the working copy specified by PATH1 into PATH2. All local changes will be preserved, but files not under version control will not be copied.

    Alternate Names

    None

    Changes

    Local disk

    Accesses Repository

    Only if exporting from a URL

    Options

    --revision (-r) REV
    --quiet (-q)
    --force
    --username USER
    --password PASS
    --no-auth-cache
    --non-interactive
    --non-recursive (-N)
    --config-dir DIR
    --native-eol EOL
    --ignore-externals
    

    Examples

    Export from your working copy (doesn't print every file and directory):

    $ svn export a-wc my-export
    Export complete.
    

    Export directly from the repository (prints every file and directory):

    $ svn export file:///tmp/repos my-export
    A  my-export/test
    A  my-export/quiz
    …
    Exported revision 15.
    

    When rolling operating-system-specific release packages, it can be useful to export a tree which uses a specific EOL character for line endings. The --native-eol option will do this, but it only affects files that have svn:eol-style = native properties attached to them. For example, to export a tree with all CRLF line endings (possibly for a Windows .zip file distribution):

    $ svn export file:///tmp/repos my-export --native-eol CRLF
    A  my-export/test
    A  my-export/quiz
    …
    Exported revision 15.
    

    You can specify LR, CR, or CRLF as a line ending type with the --native-eol option.


    The Version Control with Subversion book is licensed under the Creative Commons Attribution License v2.0.
    To submit comments, corrections, or other contributions to the text, please visit http://www.svnbook.com.