SMARTSVN Study (-)

3. Day-to-day use3.1 everyday commands

Most of the common commands you'll need is in the SMARTSVN toolbar:

• Update
• Commit
• Add
• Remove
• Move
• Revert
• Delete
• Fix
• Changes
• Annotate
• Log
• Graph

3.1.3 ADD

Add new files and folders by using Add. If there are other subfolders under the folder, the pages can be submitted together.

Use the add to schedule files or directories to add to your repository. If you ' re adding a directory that has the option to Recurse into subdirectories, which, when selected, causes all Subdirectories and files from subdirectories to be added too.

3.1.4 Remove

Use this to schedule the removal of files or directories from your repository.

Select Remove from SVN control and delete locally to schedule the files or directory for removal and to also dele Te them locally. Select Just Remove from the SVN control to schedule for removal only. After committing the changes, the files or directories remain unversioned.

By default, Smartsvn refuses to remove files or directories that has local modifications, as well as directories that con Tain modified or unversioned files. Select Force Removal (ignore local modifications, etc.) if you want to remove these items anyway.

3.1.5 Move

Use this move command to move and/or rename a file or folder. The new files and folders will be added and the old ones will be removed but will retain the removal record.

Use the this to move and/or rename a file or directory which is already under SVN control. The file with the old name is scheduled for removal, and the file with the new name scheduled for addition. This command preserves the history of the moved item.

3.1.6 Revert

Used to restore local changes to files and folders.

Use the revert the local changes of the selected files or directories. For directories, you can Revert recursively, i.e. to recurse into subdirectories. If deselected, only the properties of the directory itself is reverted.

Be careful before reverting a file or directory because all local modifications would be lost.

• Added and copied files/directories is unscheduled for addition and returned to unversioned state.
• Removed files/directories is unscheduled for removal and restored with their content and properties taken from the Pristi NE copy.
• Replaced Files/directories is unscheduled for replacement and restored with their content and properties taken from the P Ristine copy.
• Modified Files/directories is restored with their content and properties taken from the pristine copy (overwriting local changes!).
• Missing files is restored with their content and properties taken from the pristine copy. Missing directories cannot be restored, because the pristine copy is also Missing. You'll need to update your working copy instead.
• Conflicted files/directories is restored with their content and properties taken from the pristine copy, ignoring local C Hanges which caused the conflict.
• For case-changed files their original file names is restored and modifications in Contents/properties is reverted.

3.1.7 Delete

Use this to delete a local file or a folder that has no version control or is ignored. Be careful because you cannot restore files that do not have version control.

Use the To delete local files, or unversioned or ignored directories.

Be careful before deleting a file or directory because you cannot recover unversioned items.3.1.8 Fix

Use this command to determine or repair the selected file or folder. This option is rarely used.

Use this to fix or ' repair ' the selected directory or files. This option is a applicable for certain, unusual working copy states:

case-changed files

SVN repositories and working copies are generally case-sensitive. This can cause problems if working on a case-insensitive operating system, like Microsoft Windows or some file systems O n Apple Mac OS, and changing the file name ' s case (upper-case to lower-case, etc.). Because of SVN ' s working copy format and the pristine copies, it's technically not possible to handle such a file name CAs E change.

One solution is to avoid this situation by either only performing file name case changes on an operating system which supp Orts case-sensitive file names, or directly in the repository by using the repository Browser.

However, a file name case change can happen on a case-insensitive operating system, e.g. because defect tools, etc. SMARTSVN detects such invalid changes and puts the file into a case-changed file state, see Rare Primary file states. Fix Now changes the "file name case" Back to it original form as found within the pristine copy, resolving this PR Oblem.

Nested roots

A nested root (see Primary Directory States) is a working copy within another working copy which was not related to this PA Rent working copy. SVN commands ignore such nested roots. They is treated as unversioned directories.

Nested roots typically result from moving a directory from one location to another without using the proper SVN commands, Like Move. This leaves a missing directory at its original location and introduces a nested

Fix offers the following solutions for nested roots, depending on their origin:

• Mark as Copied converts the nested root to a Copied directory, with its copy location being the original Reposito Ry location. This option is a same repository as the original location, only if the available.
• Convert to unversioned strips off the working copy metadata (. SVN directories) for this directory and all of its Children. This makes the directory unversioned, so it can be added and committed afterwards. This option is all available but, in general, should only being used if Mark as Copied is not available, because unversioned directories can be added afterwards, though their the history is lost.

added-missing Directories

When you add a folder and then delete it locally (the repository and his. SVN subdirectory are missing), the folder will be in Added-missing state.

If A directory has been scheduled for addition and have been locally deleted afterwards (i.e. the directory and its. SVN su Bdirectory is missing), the directory was in Added-missing state.

Such directories is actually only a leftover entry in the parent directory ' s metadata directory (. svn). The resolution is to Revert them, and which is "what" this command does.

3.1.9 changes

Changes can show the local modification files and remote files are different places, double-click Local files can also open to view different places

changes shows you the difference between locally modified files and the pristine copy. From there several options:

• Refresh: Refresh the file contents from the file system and recalculate the differences.
• PreviousChange: Navigate to the Previous change within the currently selected file.
• Nextchange: Navigate to the next change within the currently selected file.
• Ignore whitespacefor line Comparison: When selected, both lines is treated as equal, if they only differ in the Number, but isn't in the position of whitespaces.
• take left: Overwrite the local file changes with the content of the pristine copy.
• take right: Overwrite the pristine copy with the local file changes.

When you ' re happy with any changes made, click Save.

SMARTSVN Study (-)