On Fri, Oct 7, 2011 at 12:39 PM, Adam Kocoloski wrote:
> On Oct 7, 2011, at 1:16 PM, Jan Lehnardt wrote:
>
>>
>> On Oct 7, 2011, at 19:02 , Chris Anderson wrote:
>>
>>> It looks to me as though the commits aren't flowing into the github
>>> mirror, but if we get that turned back on, github at leas
[
https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filipe Manana closed COUCHDB-1234.
--
Resolution: Fixed
Fix Version/s: 1.1
> "Named Document Replication" does not repli
[
https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123017#comment-13123017
]
Adam Kocoloski commented on COUCHDB-1234:
-
There is no 1.1.2 release of Apache C
[
https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123016#comment-13123016
]
Filipe Manana commented on COUCHDB-1234:
Jean-Pierre, I think you're talking abo
[
https://issues.apache.org/jira/browse/COUCHDB-1234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13123003#comment-13123003
]
Jean-Pierre Fiset commented on COUCHDB-1234:
As of 1.1.2, I see the same beh
Regarding the erlang-oauth and R15 compatibility,
The compilation warnings only happen in the 1.1.x because
src/erlang-oauth/Makefile.am is compiling oauth_rsa_sha1.erl while
trunk and 1.2.x are not.
Our OAuth handler is not supporting rsa-sha1 signatures, so it can be
safely ignored. I think the
On Oct 7, 2011, at 1:16 PM, Jan Lehnardt wrote:
>
> On Oct 7, 2011, at 19:02 , Chris Anderson wrote:
>
>> It looks to me as though the commits aren't flowing into the github
>> mirror, but if we get that turned back on, github at least offers tar
>> ball downloads.
>>
>> https://github.com/apac
I have finally solved the problem. Thanks to everyone.
(It was a very weird DNS configuration which does not resolve a name if SSH
is used. Once I started to use the IP address, I could connect to the
server)
>
>
> Then you should do something wrong. Works here.
>
> - benoit
>
On Oct 7, 2011, at 19:02 , Chris Anderson wrote:
> It looks to me as though the commits aren't flowing into the github
> mirror, but if we get that turned back on, github at least offers tar
> ball downloads.
>
> https://github.com/apache/couchdb/
The reasoning here is that this is an SVN mirro
It looks to me as though the commits aren't flowing into the github
mirror, but if we get that turned back on, github at least offers tar
ball downloads.
https://github.com/apache/couchdb/
Chris
On Fri, Oct 7, 2011 at 3:08 AM, Benoit Chesneau wrote:
> On Fri, Oct 7, 2011 at 11:59 AM, Andrey Som
On Fri, Oct 7, 2011 at 11:59 AM, Andrey Somov wrote:
>> git-scm.org is your friend.
>>
>>
>> Tried.
>
>
>>
>> there are the setting http.proxy to configure git with a proxy. You can
>> apply it globally or per repository.
>>
>> Tried.
>
> -
> Andrey
>
Then you should do something wrong. Works her
> git-scm.org is your friend.
>
>
> Tried.
>
> there are the setting http.proxy to configure git with a proxy. You can
> apply it globally or per repository.
>
> Tried.
-
Andrey
On Friday, October 7, 2011, Andrey Somov wrote:
>>The only platform I know of where git works less than brilliantly is
>>Windows, which ones are you struggling with?
> I think the picture is slightly different. On Windows, Git is just ugly
and
> awful, you have to install and configure a zillion o
>The only platform I know of where git works less than brilliantly is
>Windows, which ones are you struggling with?
I think the picture is slightly different. On Windows, Git is just ugly and
awful, you have to install and configure a zillion of tools to get finally
_incomplete_ support. I do not w
[
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122652#comment-13122652
]
Paul Joseph Davis commented on COUCHDB-1302:
On the face of it, I'm not a fa
[
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122650#comment-13122650
]
Benoit Chesneau commented on COUCHDB-1302:
--
We don't really need to wrap the sc
[
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122643#comment-13122643
]
Paul Joseph Davis commented on COUCHDB-1302:
Source manipulations worry me.
[
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122633#comment-13122633
]
Benoit Chesneau commented on COUCHDB-1302:
--
I don't follow Since you get a
[
https://issues.apache.org/jira/browse/COUCHDB-1302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13122622#comment-13122622
]
Paul Joseph Davis commented on COUCHDB-1302:
I'm not entirely sure what you
Could you describe your setup in more detail?
As far as I know the only public SVN access is over WebDAV on
http/https which is port 80/443. Both of these ports are supported by
the Git repository and should theoretically be allowed by all
firewalls. If you have a specific configuration that doesn
err, I should say, our svn repo was on port 80 too, and so's the git
one. *confused*
B.
On 7 October 2011 09:26, Robert Newson wrote:
> The only platform I know of where git works less than brilliantly is
> Windows, which ones are you struggling with?
>
> It's unusual to have a situation where h
The only platform I know of where git works less than brilliantly is
Windows, which ones are you struggling with?
It's unusual to have a situation where http and https are blocked but
the svn port is not. Not really sure what to suggest. A big reason
that git has an http and https transport is to
You cannot imagine how many attempts I have tried :)
For 2 days I have been busy installing, re-installing, configuring, trying,
asking, crying, crying, crying.
No progress.
But I got the message. I thought it was possible (while keeping the public
access as read-only) to port the changes as the b
the SVN repo is read-only at present in case we have to revert to it
for some reason, but otherwise there are no plans to update it.
The git repo is at: http://git-wip-us.apache.org/repos/asf/couchdb.git
If your firewall is blocking port 80 then try with https:// instead.
B.
On 7 October 2011 0
Hi all,
the source code is now maintained in Git.
But what about SVN ? Does it stay ? Are the changes ported (back) to SVN ?
My problem is that I cannot use Git. In a corporate environment (with a
proxy and firewall) and in a mixture of operating systems Git works just
awful.
Despite of the help o
25 matches
Mail list logo
