Changes between Version 119 and Version 120 of FAQ
- Timestamp:
- Sep 16, 2015, 5:21:33 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQ
v119 v120 311 311 $ git config user.email EMAIL 312 312 }}} 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: 314 315 {{{ 315 316 $ git commit file1 file2 ... -m "ticket:NUMBER - commit message" … … 325 326 326 327 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: 328 329 {{{ 329 330 $ git format-patch HEAD~1 330 331 }}} 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] 332 333 333 334 '''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.