The project settings affect the behaviour of various SVN commands. Contrary to the global preferences (see Preferences), the project settings only apply to an individual project. You can edit the settings of the currently opened project by Project|Settings.
The top of the dialog shows the Root Paths for the current project. Use Change to modify these paths, e.g. to either add other root directories or to change a root directory after the corresponding SVN working copy has been moved on your local disk.
The text file encoding affects only the presentation of file contents, for instance when comparing a file (see Show Changes) and it will only be used if for the file itself no charset has been specified by its MIME-Type property. The text file encoding settings are not relevant for SVN operations itself, which generally work only on the byte-level.
With Use system's default encoding, SmartSVN will automatically use the system's default encoding when displaying files. When changing the system encoding later, the project settings are automatically up-to-date.
Alternatively you can choose a fixed encoding by Use following encoding.
The Initial Scan settings specifies, whether SmartSVN scans the Whole project or the Root directory only when opening a project.
We recommend in general to use the Whole project option, because features like searching files in the table, etc. are relying on having the whole project structure in memory. Nevertheless, when you are working with large projects, it can be necessary to scan the file structure only on demand to avoid a high memory consumption.
The option (Re)set to Commit-Times after manipulating local files advises SmartSVN to always set a local file's time to its internal SVN property commit-time. Especially in case of an updating command (see Updating), this option is convenient to get the actual change time of a file and not the local update time.
Apply auto-props from SVN 'config' file to added files advises SmartSVN to use the auto-props from the SVN 'config' file, which is located in the Subversion directory below your home directory. These auto-props will also override other project defaults, like Default EOL Style, explained below.
Choose Keep input files after merging to always keep the auxiliary files (left, right and base) after a file has been merged by the Merge or by the Merge from 2 sources command. These files will be put into merged state (see Common Primary File States) which is similar to the conflict state however without having actual conflicts. For merged files you can use the Conflict Solver to review merge changes in detail and you can finally use Mark Resolved to mark the file as resolved and to get rid of the auxiliary files.
The Global Ignores define global ignore patterns for files/directories which should in general be ignored within the current project. This is contrary to local ignores (see Ignore Patterns), which are only related to a specific directory. You can completely deactivate Global Ignores by Deactivated. With Use from SVN 'config' file, the same ignore patterns will be used as by the command line client. To be independent of the command line client, you can enter your own patterns by Use following patterns. The Patterns are file name patterns, where '*' and '?' are wildcard symbols, interpreted in the usual way.
Choose Use MIME-type registry from SVN 'config' file to use the corresponding file which is also used by the command line client. Choose Use following patterns to specify custom Patterns, for which matching files will always be added with binary MIME-type. The wildcard symbols '*' and '?' can be used in the usual way.
This option specifies the EOL style default, which is used when adding a file (Add). For more details refer to EOL-Style.
Use In case of inconsistent EOLs to configure the behavior when adding a file with inconsistent EOLs (line endings). Add 'As Is' will automatically add the file with EOL style 'As Is'. Add as Binary will automatically set the file's type to 'Binary', see also MIME-Type. Report Error will report an error.
Usually text files are stored with 'native' EOL-Style in the SVN repository. As a result after performing SVN operations on these files your platform's native line separator will be used ('Platform'). Under certain circumstances it can be convenient to redefine what 'native' means, e.g. when a project is operated on Windows OS, but frequently uploaded to a Unix server. This redefinition can be done here by choosing the desired Native EOL-Style.
Use Set 'Needs Lock' for to specify for which files the Needs Lock should be set when they are added. With No file, the 'Needs Lock' property will be set to no file. With Binary files the property will only be set to files, which have been detected to have binary content. With Every file the property will be set to every file.
When committing files or directories, SmartSVN will scan for locked files. Choose here whether to suggest to Release Locks or to Keep Locks for those files on the 'Locks' page of the commit wizard.
Enable Automatically scan for locks and enter the corresponding interval in minutes to recurrently refresh the files' lock states. Refer to Scan Repository for details.
This option specifies the Keyword Substitution default, which is used when adding a file (Add). For more details refer to Keyword Substitution.
By default, conflicting files will receive new extensions like 'mine' or '.r4711'. Here you can specify extensions which should be preserved in case of conflicts. Choose either Use from SVN 'config' file or Use following extensions and enter the file name Extensions which should be preserved.
Projects are created by various commands. For reasons of simplicity, in most of these cases, there is no configuration possibility for the corresponding project settings. Therefore you can specify default project settings (template settings), which will be applied to every newly created project. With Project|Default Settings you can configure the same properties as for a concrete project.