Submitted patches

Page 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 [PATCH] ticket:1169 - Updated the maximum number of milliseconds allowed between two KeepAlive messages from the client.   master   2016-01-20 08:04:58     PENDING   SUCCESS 
 [PATCH] ticket:1150 - Replaced LINFO debug statements with LDEBUG in rasmgr   master   2016-01-20 08:04:20     PENDING   SUCCESS 
 [PATCH] ticket:1047 - Modified third_party makefile to install the needed header and library files to $RMANHOME/include and $RMANHOME/lib   master   2016-01-19 23:24:33     PENDING   SUCCESS 
 [PATCH] ticket:1165 - Added declaration of signal handler function   master   2016-01-19 23:24:00     PENDING   SUCCESS 
 ticket:1167 Petascope_insertdemo.sh should keep the band names after update Summary: After the last update, the default band name was changed from Gray to b1. This makes things confusing, especially when running the systemtests that make certain assumptions about the contents of your database. Test Plan: Run petascope_insertdemo.sh. Check that the name of the single field of the coverage is Gray Reviewers: dmisev, vmerticariu Differential Revision: http://codereview.rasdaman.org/D89   master   2016-01-19 18:35:59     APPLIED   SUCCESS 
 [PATCH] ticket:1142 - do not wrap RasQueryExecutionFailedException in RasQueryExecutionFailedException   master   2016-01-19 14:10:58     PENDING   SUCCESS 
 [PATCH] ticket:1164 - Update build dependencies in RPM spec files   master   2016-01-19 13:43:30     PENDING   SUCCESS 
 [PATCH] ticket:1150 - rasmgr log output is now sent to rasmgr.(PID).log as was in the old implementation of rasmgr.   master   2016-01-19 10:02:07     PENDING   SUCCESS 
 [PATCH] ticket:1119 - new type syntax in rasql   master   2016-01-18 21:22:15     PENDING   SUCCESS 
 [PATCH] ticket:1071 - rasj.jar is not installed on make install   master   2016-01-18 18:10:44     PENDING   SUCCESS 

Submit a new patch

Select your locally generated patch file below for upload. Note that the patch can only be accepted if you agree to the Rasdaman Contribution Agreement by ticking the checkbox.

See How to submit patches for a step-by-step guide, in particular regarding the patch subject format. In order to ensure quick processing and to avoid rejection, you may want to make sure your patch adheres to the rasdaman code guide.


Select the code branch below to which you want to commit (help); if you are not sure what this means just leave the default (master).



I agree to the Rasdaman Contribution Agreement.