Changes between Version 119 and Version 120 of FAQ


Ignore:
Timestamp:
Sep 16, 2015, 5:21:33 AM (9 years ago)
Author:
Dimitar Misev
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v119 v120  
    311311$ git config user.email EMAIL
    312312}}}
    313  2. When you commit your changes to your local copy put a meaningful message:
     313 1. rasdaman must be configured and compiled with `--enable-strict` to make sure that your patch doesn't introduce new warnings.
     314 1. When you commit your changes to your local copy put a meaningful message:
    314315{{{
    315316$ git commit file1 file2 ... -m "ticket:NUMBER - commit message"
     
    325326
    326327 It's best to '''always''' specify exactly the files that you want to commit, instead of committing everything with the `-a` option, so that you avoid submitting unnecessary changes in your patch.
    327  3. Then you can make the patch, e.g:
     328 1. Then you can make the patch, e.g:
    328329{{{
    329330$ git format-patch HEAD~1
    330331}}}
    331  4. Finally you can submit the generated patch to the [http://rasdaman.org/trac/rasdaman/patchmanager/ rasdaman patchmanager]
     332 1. Finally you can submit the generated patch to the [http://rasdaman.org/trac/rasdaman/patchmanager/ rasdaman patchmanager]
    332333 
    333334 '''Important:''' avoid submitting generated files like ''configure, Makefile.in'', etc. in your patch, unless the corresponding source (configure.ac, Makefile.am, ...) has been really modified.