Yeah .. from software architecture standpoint it makes sense. From a user
perspective though, it seems to me that the situation 'I made a bunch of
changes to this working copy, I want to commit it to a new branch' is a
very common situation.
Happens to me all the time when I want to keep some hacks and experiments
on my tree but not pollute the trunk with them for instance.
I notice that if I do svn switch to a branch I just created, operations
like svn mv on the working copy won't work either.. so I guess svn switch
is only reliable for modified / added files right now?
TTimo
On 17 Sep 2002 07:19:16 -0500
Ben Collins-Sussman <sussman@collab.net> wrote:
> Timothee Besset <ttimo@idsoftware.com> writes:
>
> > I encountered something, I don't know if it's intended behaviour or an
> > oversight:
>
> Yes, it's intended behavior.
>
> Think about it: there's no way that 'svn switch' knows that the two
> URLs are really the same repository, or same location. 'svn switch',
> therefore, operates exactly the same way as 'svn update', 'svn merge',
> and 'svn diff': it compares two URLs, and applies the differences to
> your working copy.
>
> However, maybe the user might be able to give a hint here. Maybe some
> optional switch could be used to mean "just rewrite all of the urls
> within .svn/entries files, and do nothing else." What do others
> think?
>
>
> >
> > I connected to my svn server through the internet with a laptop while I
> > was away. So I used an internet url like so: https://svn.internet/repos/
> >
> > Now I'm back on my LAN, and the URL is different.
> > I did
> > svn switch https://svn.lan/repos/
> > but I get
> > RA layer request failed
> >
> > I found out that this happens because https://svn.internet/repos/ is not
> > available:
> >
> > I hacked around to provide valid access to both old and new URL, did the
> > switch again and it worked. But obviously it's a workaround that might not
> > be so easy in all situations..
> >
> > TTimo
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> > For additional commands, e-mail: dev-help@subversion.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 17 14:31:22 2002