Currently, the number of projects using Git on eclipse exceeds the number of warehouses using SVN, which makes Git unique and becomes the most popular version control system for Eclipse projects. Although Git has appeared since Helios was released, migrating to Git only started after Eclipse Indigo released last summer.
While many projects have started migrating from Subversion and CVS, many projects are still using CVS or subversion warehouses. These items are likely to be cleared after the release of Indigo SR2, which expires in February this year. It is worth emphasizing that CVS will become read-only at the end of this year, but there will be no more CVS warehouses when Eclipse Juno releases this summer.
What's even more interesting is that the growth of git on eclipse does not come from the replacement of CVs warehouses, but from the replacement of SVN warehouses. Currently, CVS occupies less than 40% of the storage in eclipse, many of which are in the old days of eclipse, such as the core platform and IDE components. These projects are completely migrated to Git after the Indigo SR2 is released. The ratio of SVN warehouses has fallen so fast that less than 20% of projects are currently using subversion. This is partly because it is easier for us to automate the import of SVN projects to git without warranty on administrative files, but also partly because of historical reasons, some projects are not migrated from CVS, and new projects are more agile.
Meanwhile, on Apache, the official Apache Subversion repository already has a read-only git project image. However, when Couchdb wanted to migrate to Git, Apache didn't think it was going to work. Some people feel that this is because of the Apache Subversion project, but in fact subversion has always been the preferred repository for Apache, even before subversion projects migrated from CollabNet to Apache.
Update: Someone has proposed allowing Apache's hatching project to use git so that you can prepare some git resources in advance for the management of Git warehouses. If this works, it could lead to more projects migrating to Git in the future.
Recently, Google code allowed the project to choose between Git and HG as its distributed version control system (initially only to support Hg). Since then, git warehouses have grown and many Hg warehouses have migrated to the Git repository. Searching for git on Google code returns 5m results, while search HG returns 16m results (Google added an open support for Hg in April 2009; So, Hg has 2.5 years of history, and Git is only six months on Google code).
Atlassian bought BitBucket last year, and BitBucket also provided git hosting, in addition to the HG support that was initially provided. Although BitBucket does not disclose the number of projects using both versions of the control system, the search HG site:bitbucket.org will return 16m results and search git site: bitbucket.org returns a 5m result, which is very similar to Google code (but BitBucket offers a HG warehouse much longer than Google code).
No matter how you look at it, distributed version control systems are becoming mainstream rather than heterogeneous. Today's developers are living in the GitHub era.
Egit's Official download page is: http://www.eclipse.org/egit/download/
Then I can get 2 installation entries, I don't know the details, all installed, next is to download the relevant file automatic installation.
After installation, restart Eclipse, right-click on the established project, select Team,share Project, and then choose Git mode Share.
