Git mirrors of CVS repositories

The CVS repositories at Eclipse.org are being mirrored to read-only Git repositories. Please see the git cvs mirror page for the full list of repositories. Please note that while Git mirrors will eventually be deleted for those projects that migrate to Git, projects may exist in both places. So check the fully hosted git repositories first!

Git repositories

Eclipse projects may use either CVS, SVN or Git. The project you are looking for may not be using Git. Please see CVS Howto and SVN Howto for more information. If you are unsure which type of repository a project is using, please go to that project's home page.

List of Git repositories available

Please see to http://git.eclipse.org/. NOTE: please use the clone links at the bottom of the pages.. Do not clone from git.eclipse.org/c/

IP process implications of DVCS

Due to our rigorous IP process, the Eclipse.org use-case for a DVCS is different than that of other Open Source organizations. For this reason, an update hook is installed and must remain in place on every Git repository to ensure a clean IP provenance.

The Eclipse update hook will examine the Committer entries of an incoming push. All the committer entries must be made by the committer performing the push, or the push will fail. Furthermore, your committer ID, or the committer email address registered with your committer account at the Eclipse Foundation must be present in the Committer Email record. Here are some scenarios to help understand this restriction:

Scenario 1
Jane Contributor is Author of code. Commits to her local repo.
Jane Contributer pushes (publishes) to a committer's local repo.
Committer pushes code to git.eclipse.org will fail.
Committer cannot push code to us that they did not Commit.

Scenario 2
Jane Committer is Author of code. Commits to her local repo.
Jane Committer pushes (publishes) to another committer's local repo.
Committer pushes code to git.eclipse.org will fail.
Committer cannot push code to us that they did not commit (even if it is
from another committer).

Scenario 3
Jane Committer, known as jane@bigcorp.com to the Eclipse Foundation, is Author of code. Commits to her local repo as jane@someisp.com.
Jane Committer pushes code to git.eclipse.org will fail.
Eclipse.org does not recognize jane@someisp.com.

Scenario 4
Joe Contributor Authors code. Commits to his local repo.
Joe Contributor attaches patch to Bugzilla.
Committer applies patch to his local repo, commits to his local repo.
Committer pushes code to git.eclipse.org will succeed.
Committer can push their committed code to us, preserving the Author information in the transaction.

Referencing git repositories on the wiki

To include a reference to your Git repository on your wiki page, you can use the Git Link Template. This links to the web interface where readers can get an overview of the repository, browse the source code, and see some commit stats. Here is an example: