Git code management and problems

Libcdio: Existing folder found. Checking for updates...

Fatal: unable to access' https://github.com/ShiftMediaProject/libcdio.git/': Failed to connect to github.com port 443: Timed out

1 get the historical version code

Option 1: gitcheckout v3.0

Option 2: gitcheckout

Gittag

2 all local modifications and non-submissions will return to their original state

Git checkout.

Switching to tag history will be in a state of detached header pointer, and this modification is very dangerous. If there is no merge when switching back to the mainline, the previous modification submission will basically be lost. If you need to modify, you can try gitcheckout-b branch tag to create a branch based on the specified tag. For example, gitcheckout-b tset v0.1.0 will be developed on the branch, and then you can switch to mainline merge.

Version management

1) Application scenarios

At present, some code has been modified and submitted to SVN, then it is found to be unreasonable, and then the code is manually deleted and resubmitted

2) misunderstanding

As a result, some of the code has not been cleared, and if no one currently submits the code, you can restore the version, and if someone has already submitted the code, you must compare the historical version of the code submitted by SVN instead of modifying the code in just a few places.

Update code

1) Application scenarios

When you release a version, make sure that libraries that have been compiled by others are up to date