[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Possible issue triggered by repos reorg (including repro script)

From: Peter N. Lundblad <peter_at_famlundblad.se>
Date: 2005-04-17 14:01:31 CEST

On Sat, 16 Apr 2005, Ben Collins-Sussman wrote:

>
> On Apr 16, 2005, at 8:44 PM, C. Michael Pilato wrote:
>
> > Ben Collins-Sussman <sussman@collab.net> writes:
> >
> >> The help text could be improved. I just added more explanation to
> >> chapter 9 in the svn book as well.
> >
> > 'relocate' should have been its own subcommand, distancing itself from
> > the 'switch' operation.
> >
> >> Not yet, since the working copy, when looking at URL, doesn't know
> >> where SVNROOT ends and the "internal repository" path begins. We plan
> >> to change that someday.
> >
> > Hrm. What does this do, then:
> >
> > svn_error_t *svn_ra_get_repos_root (svn_ra_session_t *session,
> > const char **url,
> > apr_pool_t *pool);
> >
> >
>
> That's a fine solution, as long as we're okay with 'svn switch
> --relocate' hitting the network. But come to think of it, doesn't it
> already do that, some sort of repos UUID verification?
>
>
switch --relocate can't ask the repository anything before the rewrite,
since the old repository location may be dead when --relocate is used. We
really need to store the repository root URL in the entries file.

Regards,
//Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Apr 17 13:55:56 2005

This is an archived mail posted to the Subversion Dev mailing list.