You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by robertkowalski <gi...@git.apache.org> on 2014/07/18 19:20:47 UTC

[GitHub] couchdb-fauxton pull request: Fauxton: fixes after the merge

GitHub user robertkowalski opened a pull request:

    https://github.com/apache/couchdb-fauxton/pull/7

    Fauxton: fixes after the merge

    - Fauxton: Fix database view after the merge
    - Fauxton: Change Couch port to 15984
    
    @rnewson: will the port change back to 5984 in the post merge tasks?
    


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/robertkowalski/couchdb-fauxton bigcouch-merge

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/couchdb-fauxton/pull/7.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 #7
    
----
commit 5acbd98bec7c644f2e821010e8aefe6f90bc7c6c
Author: Robert Kowalski <ro...@kowalski.gd>
Date:   2014-07-18T17:10:53Z

    Fauxton: Change Couch port to 15984

commit a4a1c941d373e75eb7ee1145e250a5be0a0fa278
Author: Robert Kowalski <ro...@kowalski.gd>
Date:   2014-07-18T17:11:48Z

    Fauxton: Fix database view after the merge
    
    The type is now an Array, not a String

----


---
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-fauxton pull request: Fauxton: fixes after the merge

Posted by garrensmith <gi...@git.apache.org>.
Github user garrensmith commented on the pull request:

    https://github.com/apache/couchdb-fauxton/pull/7#issuecomment-49705912
  
    +1 this looks fine to me.


---
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-fauxton pull request: Fauxton: fixes after the merge

Posted by rnewson <gi...@git.apache.org>.
Github user rnewson commented on the pull request:

    https://github.com/apache/couchdb-fauxton/pull/7#issuecomment-49457013
  
    The port did not change to 15984, that is merely the number used for the testing cluster setup that runs three local nodes. :)


---
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-fauxton pull request: Fauxton: fixes after the merge

Posted by robertkowalski <gi...@git.apache.org>.
Github user robertkowalski commented on the pull request:

    https://github.com/apache/couchdb-fauxton/pull/7#issuecomment-50260870
  
    merged as 57923f457bb1e95f76d279b321415384676c7159


---
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-fauxton pull request: Fauxton: fixes after the merge

Posted by robertkowalski <gi...@git.apache.org>.
Github user robertkowalski closed the pull request at:

    https://github.com/apache/couchdb-fauxton/pull/7


---
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.
---