Another option is to establish a single SSH session using port mapping
and then run all of your SVN traffic across that.
Something like
ssh -L 3690:svn_server:3690 ssh_server
svn svn://localhost/
The first line says take any traffic destined for the svn port on my
machine and send it to the
On 6/16/2010 5:08 PM, Hyrum K. Wright wrote:
The Subversion client has a bad habit of treating repository access
connections (whether they be http, svn, or something else) as cheap
resources. Of course this is an invalid assumption, but it hasn't yet
been addressed by the developers.
I'm not
On Wed, Jun 16, 2010 at 4:46 PM, Les Mikesell wrote:
> On 6/16/2010 4:21 PM, Hyrum K. Wright wrote:
>>
>> The Subversion client has a bad habit of treating repository access
>> connections (whether they be http, svn, or something else) as cheap
>> resources. Of course this is an invalid assumptio
On 6/16/2010 4:21 PM, Hyrum K. Wright wrote:
The Subversion client has a bad habit of treating repository access
connections (whether they be http, svn, or something else) as cheap
resources. Of course this is an invalid assumption, but it hasn't yet
been addressed by the developers.
I'm not
On Wed, Jun 16, 2010 at 04:14:50PM -0500, Ryan Schmidt wrote:
>
> On Jun 16, 2010, at 14:41, Will Shackleford wrote:
>
> > We have a lot of trouble with the fact that subversion needs to use
> > multiple ssh connections to do a
> > single svn update. Our firewall
On Wed, Jun 16, 2010 at 2:41 PM, Will Shackleford wrote:
>
>
> We have a lot of trouble with the fact that subversion needs to use multiple
> ssh connections to do a
> single svn update. Our firewall only allows one connection through before
> you have to login to the firewall
On Jun 16, 2010, at 14:41, Will Shackleford wrote:
> We have a lot of trouble with the fact that subversion needs to use multiple
> ssh connections to do a
> single svn update. Our firewall only allows one connection through before you
> have to login to the firewall
> agai
We have a lot of trouble with the fact that subversion needs to use
multiple ssh connections to do a
single svn update. Our firewall only allows one connection through
before you have to login to the firewall
again. (which is an incredible pain)
Also tortoisesvn doesn't seem
