Skip to main content
Jump to: navigation, search


Revision as of 11:24, 13 May 2007 by (Talk | contribs) (Sending Patches)

Sending Patches

To make changes to the CDT, whether it be code, docs, JUnits, etc., you will need to send patches to the source stored on Here is the process for sending patches.

  1. Create a workspace in Eclipse for your work. Check out the CDT plugins you'd like to work on into it. The plugins are on, /cvsroot/tools. The plugins are under folder org.eclipse.cdt/all. There should be around 40 plugins there that you need to check out.
  2. Edit and test your change. This is basic Eclipse plugin development. There are a number of resources on the web and in the Eclipse help system on how to do this.
  3. Use the Eclipse Team menu to create a patch (click Team > Create Patch). Ensure that all the modified plugins are included when creating the patch. In Eclipse 3.2 and later releases you can create a patch for your whole workspace. For Eclipse 3.1, you will need to create a patch for each plugin you've changed.
  4. Attach the patch or patches to a bugzilla entry. Make sure you check off the patch box to help us find patches.
  5. Send mail to the cdt-patch list to let the committer's know there is a patch ready. See the cdt-patch info page for more information.

One of the fundamental rules that Eclipse follows is the ability to trace back who contributed what code and that the person who contributed it has ownership of the code, or has permission from their employer to contribute the code (since employers tend to own everything you write). To help keep this IP integrity going, please ensure your contributions are "clean".


  • If you are behind a firewall, you can use the proxy server at to access the CVS repository using pserver on the and port 80.

Back to the top