[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: Alan Ezust <alan.ezust_at_gmail.com>
Date: 2005-11-09 04:33:10 CET

I just discovered this today, and another annoying bit - if you do not
specify the username for an URL, it assumes you are using the same
username as that you are currently logged in as. Is there a way to
specify a different username to be inserted into that URL?

On 11/8/05, Ryan Schmidt <subversion-2005@ryandesign.com> wrote:
>
> 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:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1336
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>

---------------------------------------------------------------------
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:35:06 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.