Code management tools

Catalog

1. svn And git The difference between

1.1 GIT Is distributed and SVN It's centralized

1.2 GIT Store content as metadata , and SVN By file 　

1.3 GIT Branches and SVN Different branches of

2. frequently-used git Management tools

3. git Advantages of code management

---

Several common code management tools ：

（1）CVS

　　- Open the door to version control

　　- 1990 The year was born ,“ Ancient times ” The mainstream source code management tools

（2）SVN

　　- The full name is Subversion, King of centralized version control

　　- yes CVS The successor of , Velocity ratio CVS fast , Functional ratio CVS Many and powerful

　　- It is most commonly used in domestic software enterprises （70%-90%）

（3）Git

　　- It is the most advanced distributed version control system in the world （ Not one of them. ）

（4）ClearCase

　　- Charging centralized version control tool , Install than Windows Also big , It's slower than a snail

　　- It works ClearCase It's the world 500 strong , They have a common feature that they are rich and powerful

（5）VSS

　　- Microsoft's centralized version control tool , Integrated into the Visual Studio in

1. svn And git The difference between

1.1 GIT Is distributed and SVN It's centralized

Centralized ： A server controls all the code , The code of this server is up to date , Code operation of other computers （ Such as download 、 Submit ） It can only be executed through this server .

Distributed ： Each computer is equivalent to a server , The code is up to date , More flexible .

contrast ：Git Faster than SVN fast ;Git Than SVN flexible ;SVN Once there is no network or the server hangs up , No other computer can perform the operation , however Git You can submit to the local version library first , Wait for networking before submitting to the remote code warehouse .

1.2 GIT Store content as metadata , and SVN By file 　

All resource control systems hide the meta information of files in a similar way .svn,.cvs In the waiting folder . If you put .git The size of the directory is similar to .svn Compare , You'll find that there's a big gap between them . because .git A directory is a clone version library on your machine , It has everything on the central repository , Tag for example , Branch , Version record, etc .

1.3 GIT Branches and SVN Different branches of

Branches in SVN One of them is not special , It's another directory in the repository . If you want to know if a branch has been merged , You need to run commands like this manually svn propget svn:mergeinfo, To confirm whether the code is merged .<br> However , Handle GIT It's quite simple and interesting . You can quickly switch between several branches from the same working directory . It's easy to find branches that are not merged , You can easily and quickly merge these files .

2. frequently-used git Management tools

（1）Git Base

Git Base Use the command line method for version management , The function operation is the most flexible and powerful , Download address ：http://git-scm.com/download/win

（2）EGit

EGit yes Eclipse Of Git plug-in unit , stay Eclipse Direct operation during development EGit Very convenient , Especially for people with SVN Developers who develop plots are more enthusiastic about using , however EGit There is a lot of bug And inhuman things , Use... With caution ！

(3) TortoiseGit

stay Windows above , Imaging software TortoiseGit comparison GitHub The client is easy to use , Download address ：http://git-scm.com/download/win

3. git Advantages of code management

• It can record the whole process of a project from the beginning to the end .

• Track the changes of all contents in the project , Such as what is added , What was deleted , What content has been modified and so on .

• version control , You can clearly know the similarities and differences between each version , Such as version 2.0 Compare the version 1.0 What's more , Function, etc .

• Access control , Prevent code confusion , Improve safety , Prevent some unnecessary losses and troubles , The simple understanding is why the position does what , Don't cross the border . Such as control programmer A Have development permission for the project under development , Other projects do not have development permission , If not controlled , Then the development authority of other projects is also for programmers A to open up , If programmers A Careless and wrong operation on other projects If you delete , It will cause some losses .

• Accountability , Prevent each other from passing the buck , You can clearly know who modified which file , As a result, the project cannot run normally .

• Fallback processing , After the wrong operation is performed, there is still a chance to remedy , Such as from version 1.0 Upgrade to version 2.0, Later, I found the version 2.0 There is a mistake , At this time, you can rollback , It's more convenient .

• Conflict resolution , In the collaborative development of multiple people in the team , Conflict is a common thing , For example, there is the same file name , Functions with the same function in the same file, and so on , At this time, using source code management tools can be more convenient to resolve conflicts . The resolution of conflicts is generally in accordance with “ Copy - modify - Merge ” In principle .

If there is any infringement , Please contact to delete ！