[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn copy - tags - parent dir and create paths

From: allan juul <lambretta_at_inet.uni2.dk>
Date: 2005-01-02 11:30:36 CET

Scott Palmer wrote:
>
> 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
>

thanks for the suggestion. we might end up doing something like that.

but actually my biggest concern right now is the fact that apparently i
can *not* just tag in a single svn command. this is also hard to believe
when i think of other version control systems where one "just do it".
[eg. 'cvs tag tagname module']. one doesn't have to be bothered about
directory structures. i know subversion has a different perspective of
tags and branches but to me it's very important that tagging [or
branching for that matter] is just something you do (in a single
command) and that's it. in out case Tagging will be done very very
frequently and to ask people to create subdirectories (one by one)
before they eventually can tag is simply too much hassle IMHO.

./allan

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 2 11:33:21 2005

This is an archived mail posted to the Subversion Users mailing list.