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

Re: svn:externals forces access protocol?

From: Ryan Schmidt <subversion-2005_at_ryandesign.com>
Date: 2005-11-09 04:28:39 CET

On Nov 9, 2005, at 01:05, Steve Folly wrote:

> I appreciate the URL part can't be relative because that could get
> messed up if I copy the directory somewhere else. However, I don't
> *really* want to have to specify svnserve://svn.example.com/ on
> every line. Just /trunk/APP1, /trunk/APP2, etc. would be nice, so
> that whoever is doing the checkout will still be able to use
> whichever protocol they initially used.
> So with the prospect of all developers using the same protocol, if
> we then decide to migrate from svnserve: to http: it means I'd have
> to trudge through all those svn:externals and change them.
> Is this just a current limitation, or am I missing something here?

Yes, this is a current limitation. Externals must be set using a
fully-qualified URL including the protocol. The feature request to
allow relative and absolute paths is here:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 9 04:30:39 2005

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.