Hi
> In general, the protocol over which the connection is bundled is not a
> big performance limit. For moderately used repositories, complex
> post-commits doing silly things or doing checkouts to CIFS shares are
> such overwhelming performance hits that I've not noticed particular
> differences
On Thu, Nov 4, 2010 at 6:47 AM, David Aldrich wrote:
> Hi Nico
>
>> Hard to tell. Did you compile it yourself, or are you using your
>> distribution's Linux? And have you looked in .subversion for the
>> authorization file with your password stored in it?
>
> Thanks for referring me back to that a
Hi Nico
> Hard to tell. Did you compile it yourself, or are you using your
> distribution's Linux? And have you looked in .subversion for the
> authorization file with your password stored in it?
Thanks for referring me back to that area. I deleted the existing authorization
files and then foun
On Wed, Nov 3, 2010 at 6:26 AM, David Aldrich wrote:
> Hi
>
> I am running svn command line client 1.6.13 on Linux. Recently (possibly
> since upgrading from 1.6.6 to 1.6.13) I have found that whenever I run:
>
> svn up
>
> I am prompted for my password. I then choose to save it (unencrypted) bu
Hi
I am running svn command line client 1.6.13 on Linux. Recently (possibly since
upgrading from 1.6.6 to 1.6.13) I have found that whenever I run:
svn up
I am prompted for my password. I then choose to save it (unencrypted) but next
time around I am prompted for it again.
Any idea why this
