Yes, thats correct - only the merge action prompts for the password.
I do have read access to the root but we are still running the 1.4.6
SVN server so that's probably the problem for me here - that TSVN
tries to read a prop that doesn't exist? We will upgrade the server
in a couple of weeks, but I'm testing the client first before I deploy
it all...
//M
On Sep 13, 10:32 pm, Stefan Küng <tortoise..._at_gmail.com> wrote:
> mago wrote:
> > I'm accessing a repo in our intranet hosted by Apache 2.0 over SSL.
>
> > Example of URL:https://subversion.cpac.loc/SVN/Repo
>
> > We didn't have this problem with the 1.4.8 client, that's why I think
> > it's a bug.
>
> I assume that you have already saved the authentification data for
> commits and other command, and that only the merge still asks for it?
>
> If that's the case, make sure that you have read access to the
> repository root - a merge with 1.5 clients accesses the repository root
> a lot (the merge still succeeds if there is no access, but merge
> tracking won't work properly).
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest Interface to (Sub)Version Control
> /_/ \_\ http://tortoisesvn.net
>
> signature.asc
> < 1KViewDownload
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-09-14 11:42:23 CEST