- ‘SVN Import’ communicates directly with the repository, so no working copy or checkout is required.
- Your files are immediately committed to the repository, and are therefore available to the rest of the team.
- Intermediate directories that don’t already exist in the repository are automatically created without the need for additional switches.
‘SVN Import’ is typically used when you have a local file tree that’s being added to your Subversion project. Run the following to add a file/file tree to your repository:
svn import -m “log message” (local file/file tree path) (repository-URL)
In this example, we’re adding the contents of the “Release2” folder to the repository, in an existing ‘branches’ directory.
As already mentioned, intermediate directories do not need to exist prior to running the ‘SVN Import’ command. In this example, we’re again importing the contents of ‘Release2,’ but this time we’re simultaneously creating a ‘Release2’ directory to contain the files.
If you check the repository, you’ll see a new ‘Release2’ directory has been created. The contents of your ‘Release2’ file tree are located inside.
Want more advice on your Apache Subversion installation? We have a full series of SVN refcards for free download, covering hot topics such as branching and merging, and best practices. You can find out more at www.wandisco.com/svnref