On Jan 1, 2005, at 4:33 PM, allan juul wrote:
> hi
>
> we are considering to use the default suggested repository layout (for
> various reasons).
>
> however i think we will have a slightly annoying situation when
> developers are creating tags themselves.
>
>
> layout
> ------
> /paint/trunk/subproject_A
> /paint/trunk/subproject_A/file_A.txt
> /paint/trunk/subproject_B/
> /paint/trunk/subproject_B/file_B.txt
> /paint/branches
> /paint/tags
>
>
> Developer A maintain subproject_A while developer B maintain
> subproject_B.
>
> Now developer A wish to create a tag named v_1_0:
>
> $ svn copy \
> URL/paint/trunk/subproject_A \
> URL/paint/tags/v_1_0 \
> -m "Tagging subproject_A"
>
>
> Browsing the repository from the tags directory will now look like
> this:
>
> tags
> tags/v_1_0
> tags/v_1_0/file_A.txt
>
>
> Now developer B wish to create a tag named v_1_0:
>
> $ svn copy \
> URL/paint/trunk/subproject_B \
> URL/paint/tags/v_1_0 \
> -m "Tagging subproject_B"
>
>
> Browsing the repository from the tags directory will now look like
> this:
>
> tags
> tags/v_1_0
> tags/v_1_0/file_A.txt
> tags/v_1_0/subproject_B/
> tags/v_1_0/subproject_B/file_B.txt
>
>
> The above behavior is apparently controlled by the fact whether the
> repository directory "v_1_0" already exists or not
Why not just treat 'tags' the same as 'trunk'.. add the subprojects
directly under 'tags', then put the project specific bits in that
folder?
trunk/subproject_A/
trunk/subproject_B/
tags/subproject_A/V_1_0
tags/subproject_B/V_1_0
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 2 05:57:14 2005