Search/Navigation:
Related:
SLAC/EPP/HPS Public
Jefferson Lab/Hall B/HPS Run Wiki
S30XL-LESA/LDMX
...
Note that some (most) arguments to these commands like path/to/file are completely bogus and should be replaced by valid files in your working copy or the remote repository (depending on the command).
Checkout a Structure Node
No Format |
---|
svn co svn://repo/some/dir |
...
This command will print out general repository information like your current revision number and the repository root.
...
No Format |
---|
svn ls svn://repo/some/path/ |
Periodically, you will need to pull changes to the repository into working copy to keep it up to date.
You can update your entire local working copy by executing this command from its root directory.
No Format |
---|
svn up |
The command may also be executed with files or directories to limit the local files that are affected.
No Format |
---|
svn up some/dir some/file another/file |
...
...
This command can be used to add files:
...
The deletion will occur when you commit.
...
To delete files use this command:
...
You also need to perform a commit to delete the files in the repository and not just the local copy.
...
This command is used to commit your local changes to the repository:
...
The list of files or directories to commit is optional, but it is usually a good idea to include it.
...
svn cp src/dir/or/file target/dir/or/file
...
svn mkdir path/to/dir
...
Warning | ||
---|---|---|
| ||
Merging is an advanced operation. Always use '--dry-run' to check the results of the command before actually executing it. And always merge equivalent structure nodes when merging a branch back into the trunk, or you will screw up the trunk. |
...
svn cp m "making a branch" ^/projects/foo/trunk ^/projects/foo/branches/foo-dev
...
...
Warning | ||
---|---|---|
| ||
Making tags is an advanced operation. Most general users do not need to make tags, and for Maven projects this is done automatically during the release procedures. Never change a tag once it is made. Should changes be required, the preferred method is making them in the trunk and then making a new tag. |
...
svn cp -m "making a tag" ^/projects/foo/trunk ^/projects/foo/tags/foo-1.2.3
...
svn revert path/to/broken/local/file
...
...
This command should usually be done by the repository administrator. To have Subversion ignore files in your local copy, see the section above entitle "Global config for ignoring files".
Files can have properties on them. This can be used to alter the behavior of Subversion.
For instance, this command will cause all files with the .log extension to be ignored in the current directory.
svn propset svn:ignore "*.log" .
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...