Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: A word about Git and patches

...

Center
Deprecating entities : more information here

How to send in your contributions (or how to create patches, even with Git)

The first step is to create an account for yourself on the JIRA issue tracker and then create a new issue. Describe the contribution that you are making: are you fixing a bug, improving an existing feature, or creating a new feature? Please write as detailed a description as you can and attach screenshots if possible of what you've done. OFBIZ is a huge project, and what may be obvious to you might not be to someone else, even a committer who is familiar with the project.

...

  • Command line (see the howto below)
  • Eclipse internal command (don't use finish but rather select project to avoid the 2 1st lines in the patch)
  • A tool like Tortoise
  • If you use Git to create you patch please use "git diff --no-prefix" option to create it.
Warning
titleNo patches when moving files

Patches must never be used to move files. Else if applied we not only lose history when doing so, but also annotations.
The diff and patch commands (even "svn di" and "svn patch") are unable to keep the information about moved files, only deleted and created.

So if you are moving files, simply create patches if some files refer to the paths of the relocated files (and hence need to be changed) and tell the committers which files should be moved (from -> to)

...