Christopher Faylor wrote:
> I don't think fsh is a good idea. That could mean potentially hundreds
> of persistent ssh connections sitting around on the server.
There would at most be one per user making commits to the depot. Do
you really have hundreds of people making commits? You probably ha
On 17 Feb 2005, Marc Espie said:
> No need for fsh or anything. Didn't this feature make it into portable
> openssh ?
Yes, it did, but as usual with OpenSSH entirely without documentation
other than a changelog entry and silent change to the manpage describing
the extra options but not how to use
> Recent versions of openssh support multiple connections through one
> single authentication token (`master' connection)
That might work, but you need version OpenSSH 3.9 I think. svn.toolchain.org
is running 3.8.1p1 and gcc.gnu.org is running 3.6.1p2.
I assume both ends need to support it but I
In article <[EMAIL PROTECTED]> you write:
>Daniel Berlin wrote:
>> I should note that svn treats it's remote connections as disposable, so
>> svn+ssh will probably connect more than once for things like remote
>> diffs. So if it takes a while to authenticate, this may not be your
>> best bet if yo
Daniel Berlin wrote:
On Tue, 2005-02-15 at 15:59 +, Andrew STUBBS wrote:
I should note that svn treats it's remote connections as
disposable, so
svn+ssh will probably connect more than once for things
like remote
diffs. So if it takes a while to authenticate, this may
On Tue, Feb 15, 2005 at 09:20:57AM -0700, Bob Proulx wrote:
>Daniel Berlin wrote:
>>I should note that svn treats it's remote connections as disposable, so
>>svn+ssh will probably connect more than once for things like remote
>>diffs. So if it takes a while to authenticate, this may not be your
>>
Daniel Berlin wrote:
> I should note that svn treats it's remote connections as disposable, so
> svn+ssh will probably connect more than once for things like remote
> diffs. So if it takes a while to authenticate, this may not be your
> best bet if you are looking for blazing speed (as some seem t
On Tue, 2005-02-15 at 15:59 +, Andrew STUBBS wrote:
> > > > I should note that svn treats it's remote connections as
> > > > disposable, so
> > > > svn+ssh will probably connect more than once for things
> > like remote
> > > > diffs. So if it takes a while to authenticate, this may
> > not
> > > I should note that svn treats it's remote connections as
> > > disposable, so
> > > svn+ssh will probably connect more than once for things
> like remote
> > > diffs. So if it takes a while to authenticate, this may
> not be your
> > > best bet if you are looking for blazing speed (as som
On Tue, 2005-02-15 at 15:35 +, Andrew STUBBS wrote:
> > The ssh username is actually gcc, password foo2bar
> >
> > so svn+ssh://[EMAIL PROTECTED]/gcc/trunk
> >
> > would work (note for ssh, it's /gcc/trunk, not /svn/gcc/trunk. This is
> > because it's running svnserve with a different root.
> The ssh username is actually gcc, password foo2bar
>
> so svn+ssh://[EMAIL PROTECTED]/gcc/trunk
>
> would work (note for ssh, it's /gcc/trunk, not /svn/gcc/trunk. This is
> because it's running svnserve with a different root. Just an
> oversight,
> AFAIK :P)
Excellent. I now have a successfu
On Tue, 2005-02-15 at 12:36 +, Andrew STUBBS wrote:
> Hi,
>
> Joern and I are having difficulty accessing the subversion test repository.
>
> "svn co svn://svn.toolchain.org/svn/gcc/trunk" does not work due to the ST
> corporate firewall (don't ask - the wheels turn slowly), so I have been
>
12 matches
Mail list logo
