Yeah that's what I'm talking about. Typical case when working on code
changes, is checking out trunk or current work version, doing stuff, and
then deciding to check it in, but not on trunk, on some other branch.
In cvs this is very easy, create branch, do an update to the new branch
of your modified working copy, check in. If svn usage requires to do
something like creating the branch, checking it out fresh, and copying
over the changes manually, then it's a functionality setback.
TTimo
Greg Stein wrote:
> Hunh. I thought we were going to disallow switching with local mods. If
> somebody changes a file, then it doesn't necessarily apply to that same file
> on a different branch.
>
> At a minimum, if local mods are present on a file which is not present in
> the new location, then the switch should bail rather than tossing the
> change.
>
> Cheers,
> -g
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Sep 17 19:35:41 2002