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

Idea for implementing 'svn switch'

From: Jesper Steen Møller <jesper_at_selskabet.org>
Date: 2004-11-14 13:08:41 CET

Mark Phippard wrote:

>I think we will work on Switch and Merge next. Basically making them work
>like Tortoise does. It looks like JavaHL already has all of the code for
>this in place.
I've been thinking about how we could implement this.
First off, a single resource could be switched in a manner similar to
"Replace with revision...", using a repository browser. This is fine for
many uses.

Another feature that would make a lot of sense is to do a switch at the
SVN Repository Browser level, effectively switching ALL the projects
related to a specific location.

Consider the Subclipse projects -- switching from one branch to another
would be a lot easier if you could do it at the repository level, rather
at the three or more projects' level. For 'svn switch --relocate', this
is equally important.

Another idea is to try and guess the "switchpoint", i.e. the place in
the URL where switching is interesting (trunk, tags & branches) , merely
as a convenience. In TortoiseSVN, for instance, the repository browser
is opened at the level I selected (e.g. the project level), not at the
"switchpoint" level. So I have to cut the project's relative URL, down
to before trunk, use the repository browsing to get where I want, and
click down (or paste) to the project's relative position. We could do
Obviosly, if the repository does not contain the recommended layout, the
feature shouldn't be in the way. I also wonder if there a simple way to
tell if two URLs share common ancestry (i.e. making them suitable
switching candidates).

Just my .02€.

Received on Sun Nov 14 23:08:41 2004

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