Context Navigation

Submitted patches

Page 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 ...
Show: all, applied, pending, rejected

Patch Description	Branch	Submit Time	Status
petascope update_db.sh actually uses user and password provided in config file to create tables, avoiding table ownership issues	master	2012-02-03 18:05:16	APPLIED
rasdaman db setup script also works on scientific linux	master	2012-02-03 16:03:53	APPLIED
Fix appending of GDAL flags When appending flags to existing environment variables, ensure a space is added for separation.	master	2012-02-02 23:55:15	APPLIED
Fix usage of <iostream> in rasql_signal.cc Remove a repeated import and use the std namespace so that `endl` and friends are available.	master	2012-02-02 23:54:46	APPLIED
Remove EARLY_TEMPLATE from rasql_signal The signal handlers don't use any templated classes so there is no need to pull in this header. Also, using this header can lead to templated classes being defined in both `rasql.o` and `rasql_signal.o` after compilation which causes the linker to abort with a duplicate symbol error.	master	2012-02-02 23:54:18	APPLIED
Fix make install when --war-dir is not specified	master	2012-02-01 12:08:39	APPLIED
Fix segmentation fault when using rasdl with --debug	master	2012-01-31 16:03:03	APPLIED
Fix make dist for petascope	master	2012-01-31 13:45:30	APPLIED
Incorporate petascope makefile into automake; add --with-wardir=PATH option to specify the petascope installation path at configure time (default is share/rasdaman/war); add --with-wps=PATH option to specify the 52n WPS WAR file to be integrated with petascope, used in make wps; --with-docs now also takes care of petascope's API documentation to be installed in share/rasdaman/doc/petascope	master	2012-01-30 18:52:18	APPLIED
Fixes RPM generation	master	2012-01-30 01:25:30	APPLIED

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.

Rasdaman Contributor Agreement v1.0

These terms apply to your contribution of materials to a product or project owned or managed by us ('project'), and set out the intellectual property rights you grant to us (rasdaman GmbH, Germany, see www.rasdaman.com) in the contributed materials. If this contribution is on behalf of a company, the term 'you' will also mean the company you identify below. If you agree to be bound by these terms, fill in the information requested below and provide your signature. Alternatively, when provided together with a submission of your contribution by email, you agree to be bound by the agreement as it can be downloaded from www.rasdaman.org and that no other terms potentially supplied with your submission in addition apply.

Read this agreement carefully before signing and/or submitting.

  1. The term 'contribution' means any source code, object code, patch, tool, sample, graphic, specification, manual, documentation, or any other material posted or submitted by you to a project.

  2. With respect to any worldwide copyrights, or copyright applications and registrations, in your contribution:

    2.1. you hereby assign to us joint ownership, and to the extent that such assignment is or becomes invalid, ineffective or unenforceable, you hereby grant to us a perpetual, irrevocable, non-exclusive, worldwide, no-charge, royalty-free, unrestricted license to exercise all rights under those copyrights. This includes, at our option, the right to sublicense these same rights to third parties through multiple levels of sublicensees or other licensing arrangements;

    2.2. you agree that each of us can do all things in relation to your contribution as if each of us were the sole owners, and if one of us makes a derivative work of your contribution, the one who makes the derivative work (or has it made) will be the sole owner of that derivative work;

    2.3. you agree that you will not assert any moral rights in your contribution against us, our licensees or transferees;

    2.4. you agree that we may register a copyright in your contribution and exercise all ownership rights associated with it; and

    2.5. you agree that neither of us has any duty to consult with, obtain the consent of, pay or render an accounting to the other for any use or distribution of your contribution.

  3. With respect to any patents you own, or that you can license without payment to any third party, you hereby grant to us a perpetual, irrevocable, non-exclusive, worldwide, no-charge, royalty-free license to:

    3.1. make, have made, use, sell, offer to sell, import, and otherwise transfer your contribution in whole or in part, alone or in combination with or included in any product, work or materials arising out of the project to which your contribution was submitted, and

    3.2. at our option, to sublicense these same rights to third parties through multiple levels of sublicensees or other licensing arrangements.

  4. Except as set out above, you keep all right, title, and interest in your contribution. The rights that you grant to us under these terms are effective on the date you first submitted a contribution to us, even if your submission took place before the date you sign these terms. Any contribution we make available under any license will also be made available under a suitable FSF (Free Software Foundation) or OSI (Open Source Initiative) approved license which we choose at our discretion.

  5. With respect to your contribution, you represent that:

    5.1. it is an original work and that you can legally grant the rights set out in these terms;

    5.2. it does not to the best of your knowledge violate any third party's copyrights, trademarks, patents, or other intellectual property rights; and

    5.3. you are authorized to sign this contract on behalf of your company (if identified below).

  6. These terms will be governed by the laws of Germany. Any choice of law rules will not apply.

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.