Jump to: navigation, search

ETrice/Development/Contributions

Handling Contributions

Sources of information

Contributor

  • Pull most recent changes from origin/master
  • create patch using git format-patch... or Git GUI or TortoiseGit
 see also http://wiki.eclipse.org/ETrice/Development/Repository#Create_a_Patch_via_Git_Gui
  • attach this patch to bugzilla (don't forget to flag it as patch)

Committer

  • create a new clone from the eclipse etrice repository for this purpose to avoid interfering changes
  • create a new workspace with this contents
  • apply the proposed patch using Team > Apply Patch... Make sure to "Apply the patch to the workspace root" and set "Ignore leading path name segments" to 2
  • review the patch in the dialog by double clicking file by file and scanning the differences
  • verify the patch
  • flag the attachment (not the bug!) with iplog+
  • Commit the patch setting the contributor as author and the bug URL in the comment
  • Close the bug with a comment mentioning the Git commit (use URL, e.g. http://git.eclipse.org/c/etrice/org.eclipse.etrice.git/commit/?id=c5e939ebca6576a089a4d3c8101f61fd7553371c)
  • Verify the bug being mentioned correctly in the project's IP log http://www.eclipse.org/projects/ip_log.php?projectid=modeling.mdt.etrice (make sure iplog is flagged on the attachment and the bug is closed)

Example

https://bugs.eclipse.org/bugs/show_bug.cgi?id=337075

Hrr.protos.de 23:20, 23 February 2011 (UTC)