David Gómez wrote:
>Hi Gerco ;),
>
>On May 04 at 02:33:19, Gerco Ballintijn wrote:
>
>>>It's not really a BIG deal, but I would rather avoid having to treat
>>>some parts of the tree as serving that sort of special purpose and
>>>not as part of the organizational structure of my data.
>>>
>>This seems to be the main reason people want to have revision labels.
>>They feel the workspace root *should* be the same as the repository root.
>>This desire is however the opposite of the design choice chosen for
>>the Subversion filesystem.
>>
>
>And that's design is right for branches, but IMHO is wrong for tags.
>
This notion and use seems to rest strongly on a
one-project-per-repository assumption.
If you have a repository with multiple projects/modules, you invariably want
to tag/label specific projects. However, with revision labels all projects
share all the labels in the repository, leading to same kind of name clashes
and confusion you have with CVS tags, except worse since now even unrelated
projects in the repository share labels.
So, before you know it, there will be hierarchical revision labels for
different projects within the repository or per-project revision labels,
and we're basically back where we started, except with convoluted naming
strategy.
Gerco.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu May 5 14:13:26 2005