Ben Collins-Sussman <sussman@collab.net> writes:
> On Wed, 2004-04-07 at 07:09, Stuart Robertson wrote:
>
> > Given the above, surely Bob should be authorized to execute "svn cp
> > /trunk/ProjectA /branches/ProjectA/1.1", so as to create a new 1.1 branch?
> >
> > In my situation, however, each time I try the above example, the SVN
> > command-line prompts me for new authentication information, first asking for
> > the password for Bob, then next asking for a new userid/password combo for
> > the repository. The only way I can get this to work is to grant Bob
> > read-write access to / (that is, to add the following two lines to the
> > access-control file:
> >
> > [/]
> > @ProjectA_Owner = rw
>
> Sander Striker: any idea what's going on here?
As I noted in IM, I suspect libsvn_client is anchoring the copy commit
at the common parent of the copy source and copy target (which in this
case is '/'). This should be easy to verify.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Apr 7 16:55:07 2004