[GitHub] couchdb-fabric pull request #80: Use upgraded #mrargs{} instead of old one

Github user asfgit closed the pull request at: https://github.com/apache/couchdb-fabric/pull/80 --- 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

[GitHub] couchdb-fabric issue #80: Use upgraded #mrargs{} instead of old one

Github user rnewson commented on the issue: https://github.com/apache/couchdb-fabric/pull/80 +1 --- 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

[GitHub] couchdb-fabric pull request #80: Use upgraded #mrargs{} instead of old one

GitHub user iilyak opened a pull request: https://github.com/apache/couchdb-fabric/pull/80 Use upgraded #mrargs{} instead of old one Fixup for a previously merged commit bed5c67f9633d2837aa51c1aeb078fc671fa1e27 You can merge this pull request into a Git repository by running:

[GitHub] couchdb-couch-replicator issue #51: Format gen_server state to remove plain ...

Github user iilyak commented on the issue: https://github.com/apache/couchdb-couch-replicator/pull/51 I think I know what you mean. --- 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

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 @bebosudo you can close this PR --- 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

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user bebosudo commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 Thank you Robert! I'm looking around for some interesting db, and if couchdb will interest me I'll surely contribute to this project too. See you! --- If your project is set

[GitHub] couchdb-documentation pull request #89: Spelling error fix: fauxuton to faux...

Github user bebosudo closed the pull request at: https://github.com/apache/couchdb-documentation/pull/89 --- 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

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 and landed as 2993ccb86f9ec685a183807a54f044d42fb18592 :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

[GitHub] couchdb-fauxton pull request #808: Handle trailing params when building URLs...

GitHub user millayr reopened a pull request: https://github.com/apache/couchdb-fauxton/pull/808 Handle trailing params when building URLs for views In some circumstances, FauxtonAPI.urls() returns paths with a query parameter already appended to the end. This results in URLs that

[GitHub] couchdb-fauxton pull request #808: Handle trailing params when building URLs...

Github user millayr closed the pull request at: https://github.com/apache/couchdb-fauxton/pull/808 --- 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

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 eh typo, i was wanting to say: "i was also super excited when i sent my first PRs. for most people it is exciting and it can be unpleasant." -- edited the comment --- If your

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 @bebosudo just saw your question. some parts of the docs are still outdated or even incomplete. it was a tradeoff, we had to ship 2.0 at some point. (with a 2 year

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 no worries, you are doing great! :) btw: i was also super excited when i sent my first PRs. most people are and it can be unpleasent. i'm still excited

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user bebosudo commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 (first pull request on a big open source project, I got excited :-P ) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

[GitHub] couchdb-documentation issue #89: Spelling error fix: fauxuton to fauxton.

Github user robertkowalski commented on the issue: https://github.com/apache/couchdb-documentation/pull/89 awesome, thank you! +1 --- 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

[GitHub] couchdb-documentation pull request #89: Spelling error fix: fauxuton to faux...

GitHub user bebosudo opened a pull request: https://github.com/apache/couchdb-documentation/pull/89 Spelling error fix: fauxuton to fauxton. I was following the intro and I spotted some spelling errors. Moreover, why the doc intro is so updated compared to this file?

[GitHub] couchdb-fauxton issue #807: Couchdb 3224

Github user sergey-safarov commented on the issue: https://github.com/apache/couchdb-fauxton/pull/807 Hello @robertkowalski I found that when edited document in database with "/" symbols in name and pressed "Save Changes" button, then list of database documents is not displayed.