Log

Use Query|Log to display the change history of the selected file/directory. On the Configuration page you can specify, how far back in history the changes should be displayed.

Select Stop logging on copied locations, to make SmartSVN not trace further changes after it has encountered a revision where the file/directory has been copied from another location.

Select Include merged revisions to also fetch the originating revisions for revisions which have been merged. This option recursively descends into merged revisions and depending on the number of merges that have affected the file/directory this may result in a large or even huge number of reported revisions.

On the Advanced page, you can configure the usage of the Log Cache. By default, the Log Cache is Enabled with updating, which will speed up logging. You can also choose Enabled without updating to skip updating the cache from the repository, before it is queried. With this option you can perform logs without requiring any connection to the repository. However new revisions from the repository won't be displayed. With Disabled the log command will be performed directly against the repository. This can be helpful if your Log Cache is obsolete due to changes in the repository of already cached log data, see Log Cache for details.

Note

When using Include merged revisions with the Log Cache being Enabled, it will still be necessary to perform the Log directly against the repository.

The Log may also be performed directly against the repository if the corresponding Log Cache is currently updating a large number of revisions from the repository. The reason is that instead of waiting for the Cache update to be finished it will in general be faster to perform the Log directly.

When Log HEAD instead of working revision is selected, the Log will be performed against the selected directory's/file's URL at HEAD. This will report even revisions for the URL which are newer than the corresponding working copy revision. The disadvantage of this option is that the Log might fail, because the URL does no longer exist within the repository at HEAD.

After you have configured the command, click OK to proceed. Depending on the configuration the upcoming Log frame will show the resulting log as a directory/file tree or as a list of single file revisions. For details refer to Log.