You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by iilyak <gi...@git.apache.org> on 2015/01/30 00:15:19 UTC
[GitHub] couchdb-chttpd pull request: 2561 make config api consistent
GitHub user iilyak opened a pull request:
https://github.com/apache/couchdb-chttpd/pull/21
2561 make config api consistent
This PR should go with https://github.com/apache/couchdb-config/pull/2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/iilyak/couchdb-chttpd 2561-make-config-API-consistent
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/couchdb-chttpd/pull/21.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #21
----
commit 469c85383b420ccafa0a8dd10382b9b9d62bb9b6
Author: ILYA Khlopotov <ii...@ca.ibm.com>
Date: 2015-01-29T21:33:57Z
Update config_listener behaviuor
COUCHDB-2561
commit daf20e6bff657ccda580fa55a8d89465bc98fde0
Author: ILYA Khlopotov <ii...@ca.ibm.com>
Date: 2015-01-29T21:34:31Z
config:get/3 is more strict now
The config:get/3 supports only following types for default argument
- atom `undefined`
- string (list)
- boolean
- float
- integer
COUCDB-2561
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] couchdb-chttpd pull request: 2561 make config api consistent
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/couchdb-chttpd/pull/21
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---