On Wed, May 15, 2013 at 12:06 PM, Andrew Reedick
<andrew.reed...@cbeyond.net> wrote:
>
>
> Isolating change is a fundamental tenet behind branching. The fact that an
> "outside" change can affect a branch (and a tagged baseline) is wrong by
> definition.
>
OK, but that means you need to anchor the concept of 'this branch' to
the top of the tree that you consider isolated. There is no such
concept now.
> Telling folks to never change their branching structure is a bit
> short-sighted given the lack of reliable precognitive ability in general and
> that occasionally folks like to clean up the branches and tags dir when
> they're cluttered with dozens of old branches and tags. Telling folks not to
> run 'svn mv tags/1.0* archive/' simply isn't helpful.
So, do you want to disallow such moves - or make merge tracking aware
of all the possibilities in the repository tree?
> Plus, telling people not use to svn's touted directory manipulation features
> because of side-effects is a bit self-defeating.
Not if you want it to act like SCM's that have branches that don't
allow such things.
--
Les Mikesell
lesmikes...@gmail.com
