Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CALtvvM9AM5Qmhn1626n0Uo687jyoDujfhgd3qxPOy1m+9eHg+Q@mail.gmail.com>
References: 
 <CALtvvM_vKY5NVO0A5yTviMopP34zGj+wmeAVwUUOgOO0J22K3g@mail.gmail.com>
	<CABvT1DFcWExVLJtZYvDeJuZY8+UweWMD_CtqyQUt7pR8Mt-vDw@mail.gmail.com>
	<CALtvvM9AM5Qmhn1626n0Uo687jyoDujfhgd3qxPOy1m+9eHg+Q@mail.gmail.com>
Date: Fri, 7 Oct 2011 09:26:35 +0100
Message-ID: 
 <CABvT1DH-7weT+9XFxrwa2D-AKH8SKg31bEkttXesM-4F+uX0tw@mail.gmail.com>
Subject: Re: Git to SVN
From: Robert Newson <rnewson@apache.org>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

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 work with (or 'around',
if you're so inclined) proxies and firewalls.

B.

On 7 October 2011 09:13, Andrey Somov <trophybase@googlemail.com> wrote:
> 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 batch process on the SVN
> server. But this must be a general task for Apache.
>
> -
> Andrey
>