Jump to: navigation, search


< ETrice‎ | Development
Revision as of 05:04, 9 May 2011 by Hrr.protos.de (Talk | contribs) (Example)

Handling Contributions

Sources of information



  • 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
    • example: git commit -a --author="Firstname Name <email@mycompany.com>" -m"applied patch for a really nice feature: https://bugs.eclipse.org/bugs/show_bug.cgi?id=339803"
  • 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)




The following Bash command can be used to search missing about.html files (thanks to the MoDisco Wiki pages):

 $ find org.eclipse.mdt.modisco* -name build.properties \! -exec grep -sq about.html {} \; -type f -print

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