Re: svn commit: rev 6715 - in branches/neon-0.24

"Sergey A. Lipnevich" <sergey@optimaltec.com> writes:
> Yes it does, thanks! My only concern here is that in the middle of
> rebranching I'd have to save and then reapply changes that didn't make
> it to the trunk.

You don't have to save them -- they're already saved in the
repository, in the old version of your branch.

> I guess the decision on the merge strategy has to be
> made on a per-project basis. In a corporate setting, I'd be reluctant
> to use Subversion's rebranching, out of fear of losing unmerged
> changes (it's more difficult to explain this to team members to begin
> with).

The only kind of change you ever need to fear losing is an uncommitted
one, and that's true no matter what kind of branching scheme you're
using. Of the two branching schemes we're discussing, neither
involves saving uncommitted changes in a working copy while some other
operation is performed.

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 22 04:03:58 2003