Jump to: navigation, search

Difference between revisions of "Git for Committers"

(Contributing to EGit)
m (Setting up git)
Line 12: Line 12:
 
** Something along the lines of [http://ketan.padegaonkar.name/2009/01/24/using-mercurial-with-eclipse-cvs.html Ketan's blog for Mercurial]
 
** Something along the lines of [http://ketan.padegaonkar.name/2009/01/24/using-mercurial-with-eclipse-cvs.html Ketan's blog for Mercurial]
 
*  Known Issues and Gotchas
 
*  Known Issues and Gotchas
** Initially pulling from CVS into a repo puts HEAVY load on the Eclipse CVS server ... better clone an existing git repo if available
+
** Initially pulling from CVS into a repo puts HEAVY load on the Eclipse CVS server ... better clone an existing git repo if available(Can be used as a a form of a torrent, it is possible to pull from someone else team, and sync with eclipse servers, they're all the same repositories)
  
 
= Using the EGit integration=
 
= Using the EGit integration=

Revision as of 13:54, 6 March 2009

Background

  • bug 257706 Host a git repository on Eclipse Foundation servers, support git as the repository of Eclipse projects
    • bug 257706#c63 Mike M. on potential problems with git at the Foundation
  • EGit/Proposal

Setting up git

Using the EGit integration

Contributing to EGit

If you want to get involved with EGit, please see our Google Code project site:

 http://code.google.com/p/egit/

Known open issues are listed here, along with the clone URL for the Git repository containing the project's code. Loading it into Eclipse is as simple as importing the existing projects from the checked-out repository. Please see SUBMITTING_PATCHES in the top level directory for information on how to send contributions in.

Known git repositories for Eclipse projects

Meetings and Resources