Svn basic common operation settings and svn common operation settings

Svn basic common operation settings and svn common operation settings

The code management tool is a bit tricky at the beginning, but once it is permanent, it will find that all these routines are recorded.

 

After the managed code is in conflict, I still want to re-execute it. There is a omnipotent resetting operation, that is, re-associating the svn project. In the past, I sometimes changed the address and found many conflicting problems, because the file was created before, but then deleted on the server, the result conflict with the address, and find that the conflict, you can not restore, what to do, re-join it, saving trouble.

You can also delete the svn file.

 

Then checkout

Note the path here. You need to switch to the project root directory in checkout, otherwise it will not match your project address, because we generally pull the code from the project root directory drop-down.

 

 

The Association on android studio is also simple.

 

As long as you have an address pair, you can display the path below the address, and then checkout you will find that you are logged on, there will be a specific directory, then you can check the root directory of the project, and click the above menu to switch to the address. If the account has no permissions, a prompt will be displayed, and the corresponding address will be associated.

Sometimes there will be no menu above. You just need to add a project in setting again.

 

 

The same is true for the first Association.

Git is basically similar to this operation. The difference is that git needs to submit the code in push first, and push is to the server. svn seems to automatically push the code to the server after it is submitted.

Ignore code. You can right-click the shortcut key to add it to ignore.

The above are common operations.