Feasibility Analysis of replacing SVN with GIT

Document directory

• Conclusion

I tried git and felt that git has the following advantages:

1. Version library Localization
   -- Each developer has its own version control library, and can execute code submission and branch creation on its own version library. For example, do developers think there is a problem with the code they submit? It doesn't matter, because the version library is its own, rollback history, repeated submission, and merge branch won't affect other developers.
2. Because it is a private local version library"Real" offline work
   Possible.
3. Only when necessary will it be merged with the public version library. Each developer will save an image of the public version library locally, when submitting the image, you can synchronize it with the public version library to update the image,You can create updates for the public version library based on this image and your own private version library.
   This patch can be used to upgrade the public version library through email, HTTP, and other transmission methods.
4. Git has powerful "comparison" functions,Merge files faster than SVN
   .
5. Pollution-free git
   Git generates only one. Git directory for each project. All version control information of this project is in this directory, and The. SVN directory is not generated in every directory as SVN does.

Currently, git has the following shortcomings:

1. Git lacks the detailed permission management function, which is related to the background and culture of git. Git adheres to the spirit of free and open Linux and does not have the concept of permission management, in addition, it is difficult to change in a short period of time. We can only expect third-party tools to make up for this defect. For example, in Linux, the permission management of the GIT version library is generally done through the user permission management of the Linux system. SVN has many third-party management tools to choose from.
2. Although git can merge files, it does not provide a graphical merge tool. For example, if you need to manually compare files, you need to use tools like tortoisemerge and araxis merge in windows ...... We know that human comparison is essential.
3. Git's Eclipse plug-in has limited functions. Many operations still need to rely on command lines. It is said that there are still some bugs.

Conclusion

• Git is a real distributed version management tool.
  Each user has his own code library, which is different from SVN. The biggest benefit of this difference is that it is very convenient to track local modifications, and different code libraries in SVN cannot be switched. However, the user interface of the svn client is much more user-friendly than git, especially SVN is built on the familiar CVS model.
• Git is very suitable for projects with highly dispersed development organization forms such as Linux kernel, which relies heavily on email for communication.
• Git is also suitable for the development of small teams who communicate via email. Git provides many considerate and small functions, so I won't talk about it here.
• Company Development is a relatively concentrated work modelHigh requirements on time and collaboration Efficiency
  It is better to use tools such as CVS and SVN based on the central version control library. After all, they are more mature and friendly than git in this regard.

Some git Resources

• Tortoisegit-tortoisesvn git version

It is porting tortoisesvn to tortoisegit the latest release 0.5.1.0 this release can complete regular task, such commit, show log, diff two version, create branch and tag, create patch and so on. welcome to contribute this project.Using Windows yet.

• Git Eclipse plug-in

Http://www.jgit.org -- the GIT Eclipse plug-in mentioned above, installed on the play will know ......