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

RE: svn:external and server migration

From: Lira Olavo <Olavo.LIRA_at_gemalto.com>
Date: Thu, 18 Sep 2008 23:36:46 +0200

Oh yes, Cristal clear!

Thank you so much!!

Olavo Lira

-----Original Message-----
From: Purple Streak [mailto:mrpurplestreak_at_googlemail.com]
Sent: Wednesday, September 17, 2008 3:07 PM
To: Lira Olavo
Cc: svn [usr]
Subject: Re: svn:external and server migration

2008/9/17 Lira Olavo <Olavo.LIRA_at_gemalto.com>:
> What they mean by " relative to the scheme" for instance?
> Could you give an example how this 2 old-fashioned properties would
> like when using the new format?
> Link 1: DirB https://server/repositoryA/Project1/DirA
> Link 2: DirA https://server/repositoryB/Project2/DirB

relative to the scheme just means you can omit the https: at the front - e.g.

//server/repositoryA/Project1/DirA DirB
//server/repositoryB/Project2/DirB DirA

All this means if that if at some point a client connect to the
repository with svn:// (instead of https://) then the external would
still work

If the repositories are on the same server (like the 2 above would be)
then you can go one better and omit the //server bit to give...

/repositoryA/Project1/DirA DirB
/repositoryB/Project2/DirB DirA

Now when the client gets the external it takes the schema (svn:// or
https://) AND the server name from it's connection and prepends that
to the external before getting it.

Does that make it clearer?

  • application/x-pkcs7-signature attachment: smime.p7s
Received on 2008-09-18 23:37:18 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.