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

confusion caused by "switch working copy to new branch/tag"

From: Wim Coenen <wcoenen_at_gmail.com>
Date: Fri, 10 Oct 2008 19:12:53 +0200


TortoiseSVN supports the scenario where you can "shelve" some
unfinished local modifications directly to a branch. This can be done
by using the "Branch/Tag" action on your working copy root and
selecting "Create copy in the repository from <working copy>". This is
quite useful.

When the user immediately wants to continue working on the branch he
will enable the "switch working copy to new branch/tag".

There are some issues with the implementation of this last feature.
The progress dialog does not distinguish very clearly between the
commit progress and the switch progress. My proposal: prefix the
progress messages with "COPY: " and "SWITCH: ".

More details on why there is confusion sometimes:

Sometimes the switch fails, e.g in some cases where one of the local
modifications was a file addition. I have seen one of my colleagues
struggle with this because he thought the commit failed, while in
reality the switch had failed and stopped halfway.

Furthermore, if the local modifications include binary files,
subversion will unnecessarily mark these files as conflicted during
the switch. (I realize that this cannot be fixed in TortoiseSVN.) This
results in more confusion: the user thinks he can't commit because
there are conflicts which he didn't notice before. Again, it might be
easier to understand what happened if the commit progress and switch
progress were clearly distinguishable.


Wim Coenen

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-10-10 19:13:06 CEST

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

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