Can anyone help me explain in detail how Svn hits the version number and how to restore the previous

First of all, a milestone is when a certain amount or goal of the software function is reached. When the software reaches this goal or completes the corresponding functions, you can make a baseline here, and then type a version number after the test is completed.

The way to type the version number is to right-click tortoisesvn-->branch tag in the directory where you have permissions

The source is the folder directory you just right-clicked, and the destination is the path where the version is stored.

As for the restoration, unless the machine is broken, it is generally not possible to restore SVN casually, and the restoration method has been said upstairs, so I will not repeat it.

Hope mine can help you.

Restore the previous version, which can be used from the command line.

svn up -r 444

is what you want to restore, and 444 is the previous version number.

In the process of writing, it is inevitable that some errors need to be modified, or you want to modify from the previous file, which involves the tracking of the version. Here are a few ways to roll back a version:

1.One recommended way is to export the version you need directly, and then overwrite your latest version with the version you exported, so that you don't lose your newly created files and get the latest SVN versioning.

Procedure: tortoisesvn show log Select the version to be rolled back Right-click export.

After that, overwrite the modified file to your latest version, and commit.

2.If you have a project and you want to discard these changes without committing it, you can simply select tortoisesvn revert to update to the latest version of the project.

3.If you want to revert to a version, you can simply select Tortoisesvn Update to Reversion, so that we can roll back our version to the version you selected, in which case svn doesn't show any conflicts, and the newly created file is still there, but in this case you can't do it directly on the version you reverted, because svn's version control is still on the latest trunk. We need to update and resolve the conflict.

4.You can simply select Revert Changes from this revision, so you can resolve the conflict and commit. However, the downside of this method is that all the files you created are gone, and the entire project is reverted to the previous version.

5.You can roll back to the version you need from the log, select the version you need from the log, and then update item to reversion, in which case svn doesn't show any conflicts, and the newly created file is still there, but in this case you can't do it directly on the version you rolled back, because svn's version control is still on the latest trunk. We need to update and resolve the conflict.