Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Jetty/Contributor/Contributing Patches"

Line 9: Line 9:
 
From the top level of the cloned project:
 
From the top level of the cloned project:
  
> git diff > ######.patch  
+
<tt>git diff > ######.patch</tt>
  
 
The hash marks should be the bugzilla issue that you will be attaching the issue to.  All patches coming into jetty @ eclipse much come in through bugzilla for IP tracking purposes.  Depending on the size of the patch the patch itself may be flagged as +iplog where it is subject to lawyer review and inclusion with our iplog from here to eternity.  We are sorry we are unable to apply patches that we receive via email.  So if you have the bugzilla issue created already just attach the issue and feel free to bug us on IRC to take a look.  If there is no bugzilla issue yet, create one, make sure the patch is named appropriately and attach it.
 
The hash marks should be the bugzilla issue that you will be attaching the issue to.  All patches coming into jetty @ eclipse much come in through bugzilla for IP tracking purposes.  Depending on the size of the patch the patch itself may be flagged as +iplog where it is subject to lawyer review and inclusion with our iplog from here to eternity.  We are sorry we are unable to apply patches that we receive via email.  So if you have the bugzilla issue created already just attach the issue and feel free to bug us on IRC to take a look.  If there is no bugzilla issue yet, create one, make sure the patch is named appropriately and attach it.

Revision as of 09:15, 2 August 2011



How to contribute a patch to Jetty @ Eclipse.

Git Diff

The simplest way to contribute a patch is to make a modification to a cloned copy of jetty and then generate a diff between the two versions.

From the top level of the cloned project:

git diff > ######.patch

The hash marks should be the bugzilla issue that you will be attaching the issue to. All patches coming into jetty @ eclipse much come in through bugzilla for IP tracking purposes. Depending on the size of the patch the patch itself may be flagged as +iplog where it is subject to lawyer review and inclusion with our iplog from here to eternity. We are sorry we are unable to apply patches that we receive via email. So if you have the bugzilla issue created already just attach the issue and feel free to bug us on IRC to take a look. If there is no bugzilla issue yet, create one, make sure the patch is named appropriately and attach it.

Git Format Patch

  • to be written *

Back to the top