|Version 20 (modified by pbaumann, 21 months ago) (diff)|
How To Provide A Fix
You developed a fix or some new functionality? We are grateful for your contribution.
Of course we like any useful information, but best (and fastest) for inclusion is to be in sync with our development tools. The following details are provided to help in this respect.
- All our development is in Linux. Please consider this for your code.
- We use git as version management tool, so you may want do do that too. Check out from the repository using:
$ git clone git://rasdaman.org/rasdaman.git $ git config user.name "Name Surname" $ git config user.email email@example.com
- After ensuring the tests are successful (see RasdamanTestSuites), stage and commit your changes:
$ git add <file1> <file2> <dir1/> <dir2>/*.java ... $ git commit -m "My brief explanation of the patch"
- Prepare your patch package through:
where n is the number of last commits that you want to create patch files for. Put these files in one archive (preferably .tar.gz).
$ git format-patch -n
- Upload your patch file (or a .tar.gz archive in case of several files) using Patch Manager. You will have to accept the Contributor Agreement. Without your stated consent we unfortunately cannot accept it, due to legal reasons.
Linus Torvalds' suggestions on merging and rebasing : link.
Further tips (use 'Git*' naming rule for new pages):