On Tue, May 21, 2013 at 3:32 PM, Andrew Reedick
<Andrew.Reedick_at_cbeyond.net> wrote:
>
> We'll have to agree to disagree. We're back at the low level "managing dirs" versus high-level "managing baselines" arguments/thinking/paradigms.
>
We're not completely opposed here. I can see the value of being able
to note the 'top' of where you think a branch starts and constrain
subsequent 'branch related' operations to that and things with the
same parent revision history. But I can also see the value of being
able to organize your branches under a parent tree to separate
qa/release/feature/experimental/etc. sections, so I don't think
completely hiding the path to branches is the right answer. And
given subversion's ability to check out directories 'above' your
project or branch level, I don't see how you can avoid a literal
mapping into directories even if that doesn't match the more typical
use.
In any case, if you have ever published/announced a URL to your branch
to the group that will use it, you have a bigger problem than with the
tool itself if you change that location after the fact. Rather than
trying to change history with a move you want to pretend didn't
happen, maybe it would be better to just do a copy and have everyone
aware that the location is new.
--
Les Mikesell
lesmikesell_at_gmail.com
Received on 2013-05-21 23:05:31 CEST