On 21.05.2013 20:26, Branko Čibej wrote:
> On 21.05.2013 19:50, Andrew Reedick wrote:
>> Ooops. All of your immutable, static, locked down, haven't been touched in months tags now have a new revision, and they all share that revision in common. The parent dir change from "/tags" to "/project1/tags" is visible under the tag1, tag2, etc. baselines because svn doesn't know that "^/project1/tags" isn't/shouldn't be part of your "tag1", "tag2", etc. baselines.
> In fact, it should, because you renamed the tags. The misconception is
> that the names of the tags is "tag1" and "tag2"; that is not the case.
> The names are /tags/tag1 and /tags/tag2 before the rename, and whatever
> the paths are after the rename.
>
> You cannot identify a directory (or branch or tag) just by its basename,
> only the whole path is a unique identifier (within the repository).
Just to be clear -- I agree that the the result of 'svn log
--stop-on-copy' changes is confusing. And, as I said (much) earlier in
this thread, that's an unfortunate side effect of how renames are
currently implemented. Personally I've always viewed the --stop-on-copy
as a hack, and we really should invent a better way of identifying
branch points.
-- Brane
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com
Received on 2013-05-21 20:32:33 CEST