Submitted patches

Page 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60  ...
Show: all, applied, pending, rejected
Patch Description Author Branch Submit Time Action Status Test Status
 [PATCH] ticket:2508 - improve INSPIRE coverages documentation   master   2021-11-12 10:20:01     PENDING   SUCCESS 
 [PATCH] ticket:2508 - Petascope - supports INSPIRE coverages in WCS GetCapabilities result   master   2021-11-11 15:07:36     PENDING   SUCCESS 
 [PATCH] ticket:2509 - WMS - WCPS fragment to compute difference between two slices in WMS style   master   2021-11-10 11:45:03     PENDING   SUCCESS 
 [PATCH] ticket:2506 - set default 4GB limit for petascope with JAVA_OPTS if undefined   master   2021-11-01 16:47:18     PENDING   SUCCESS 
 [PATCH] ticket:2504 - fix compilation with -DUSE_GRIB=OFF   master   2021-10-22 07:31:06     PENDING   SUCCESS 
 [PATCH] ticket:2502 - script for automating issue reporting, ticket:2470 - remove --service secore from start_rasdaman.sh and stop_rasdaman.sh as it is now part of petascope   master   2021-10-20 17:33:29     PENDING   SUCCESS 
 [PATCH] ticket:2480 - fix test case failing on centos7   master   2021-10-04 23:04:55     PENDING   SUCCESS 
 [PATCH] ticket:2491 - rasdaman logs should not be world-readable, ticket:2475 - set embedded petascope deployment by default, ticket:2449 - fix build error on non-unity build, ticket:2413 - start_rasdaman.sh should exit if executed by root, ticket:2387 - unset http_proxy in start_rasdaman.sh   master   2021-10-01 20:18:11     PENDING   SUCCESS 
 [PATCH] ticket:2441 - wcst_import validates band's name in the general recipe   master   2021-10-01 16:51:14     PENDING   SUCCESS 
 [PATCH] ticket:2465 - petascope enhances time to load basic coverages to cache when petascope starts   master   2021-09-30 15:05:02     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.