Github user garrensmith commented on the issue:
https://github.com/apache/couchdb/pull/453
I'm closing this. @nickva did a much better fix and its in master
---
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
Github user janl commented on the issue:
https://github.com/apache/couchdb/pull/453
> It's both, but it seems the preferred way is to use the github repo's and
use gitbox as a fallback
There is no preferred way. Individual developers can pick either route.
As for
Github user garrensmith commented on the issue:
https://github.com/apache/couchdb/pull/453
It's both, but it seems the preferred way is to use the github repo's and
use gitbox as a fallbackÂ
All misspelling thanks to my iPhone.
On Thu, Mar 9, 2017 at
Github user kxepal commented on the issue:
https://github.com/apache/couchdb/pull/453
I'm with @wohali.
---
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
Github user wohali commented on the issue:
https://github.com/apache/couchdb/pull/453
I'm confused. Are the canonical URLs for our repos now at github.com or
gitbox.apache.org? I thought it was the latter, which would make this PR
incorrect.
---
If your project is set up for it,
Github user lostnet commented on the issue:
https://github.com/apache/couchdb/pull/453
My automated builds are using anonymous clone over https, so git over ssh
fails on the github hostkey, etc. Maybe https urls would work correctly for
both configurations:
```
-{docs,
