dune-fem  2.4.1-rc
Some Notes on Using Subversion

Updating Your Working Copy

To update your working copy, simply type

svn update
Note
You can also downgrade to an older revision by
svn update -r <revision>
Alternatively, use the date DD.MM.YYYY specify the revision by
svn update -r "{YYYYMMDD}"

Obtaining a List of Files You Changed

When making changes one simetimes forgets all the files that have changes. Subversion can give you an overview over the changed files by

svn status
Note
Files marked by a question mark have not been added to version control. You should add them, before committing your changes.

Committing Your Changes to the Repository

After making changes to your working copy and successfully testing them, you have to commit them to the repository before others can use them. To do so, use

svn commit -m "<message>"
Note
You can explicitly specify which files should be committed by adding them to the command line.

Adding files to version control

After creating a new file that shall be under version control, you have to type

svn add <name>
Note
The file will not be in the repository until you commit your changes.
You cannot simply remove the newly added file from version control before it has been committed. If you want to do so, use
svn rm --force <name>
The same applies to the move operation

Removing a File from Version Control

To remove a file under version control, you can use

svn rm <name>
Note
Subversion will actually delete the file, so if you want to keep it you should create a backup first.

Moving version controlled files

If a file is under version control and you want to rename or move it, you should not do so yourself, but let subversion do it for you:

svn mv <oldname> <newname>

Subversion does not only move the file, but also remembers the version history of that file.

Note
Moving the file by hand, telling subversion to delete the old file and adding the new one is a bad idea. Subversion does not know the files are actually the same and hence cannot merge differences (or detect conflicts).

Specifying File Names that Subversion Should Ignore

When looking for changed files, subversion should automatically some files generated during compilation like object files, log files, etc. Subversion keeps a seperate list which file patterns to ignore for each directory. You can edit that list by the following command:

svn propedit svn:ignore <directory>
Note
Changes to properties must be committed, too.