Submitted patches

Page 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 ticket:1137 - Using wcst_import in petascope_insertdemo.sh (http://codereview.rasdaman.org/D65)   master   2016-01-14 14:23:38     APPLIED   SUCCESS 
 ticket:1134 - Fixed bug in wcs-client GetCoverage core tab that prevented slicing at the default value Summary: Removed faulty assumption about the slicing point. Test Plan: Open the wcs-client, select a coverage, go to the GetCoverage tab and check the slicing radio button. Pressing Download Coverage will download the selected coverage sliced at the values specified in the box. Reviewers: mdumitru, vmerticariu Differential Revision: http://codereview.rasdaman.org/D71   master   2016-01-14 13:50:01     APPLIED   SUCCESS 
 [PATCH] ticket:1132 - Missing detail information in log file of system test (test_wcs, test_wcps,...) (http://codereview.rasdaman.org/D63)   master   2016-01-14 13:33:28     PENDING   SUCCESS 
 [PATCH] ticket:1145 Boost exception is required by rasmgr but it isn't actually needed   master   2016-01-14 10:02:57     PENDING   SUCCESS 
 [PATCH] ticket:1144 git init needs to be run in source root for git < 1.8   master   2016-01-13 16:18:42     PENDING   SUCCESS 
 [PATCH] ticket:1135 - reconfigure the debug symbols requirements   master   2016-01-13 10:15:50     PENDING   SUCCESS 
 [PATCH] ticket:732 - SECORE definition is not valid and need to validate all definition (http://codereview.rasdaman.org/D47)   master   2016-01-13 09:52:40     PENDING   SUCCESS 
 [PATCH] ticket:1136 - Fix format specifiers for oid in partinsert.cc   master   2016-01-12 21:33:39     PENDING   SUCCESS 
 [PATCH] ticket:1104 - generate java proto files if they are missing   master   2016-01-12 18:11:29     PENDING   SUCCESS 
 [PATCH] ticket:1135 - reconfigure the debug symbols requirements   master   2016-01-12 16:34:03     REJECTED   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.