Re: confusion caused by "switch working copy to new branch/tag"
Wim Coenen wrote:
> 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.
The dialog titles already have the command in it.
Also, the first line in the progress dialog tells you the exact command.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
Received on 2008-10-10 21:41:38 CEST
This is an archived mail posted to the TortoiseSVN Users