[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: Scott Palmer <scott.palmer_at_2connected.org>
Date: 2005-01-02 20:06:38 CET

On Jan 2, 2005, at 5:30 AM, allan juul wrote:

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

Just create the tags/subproject/ folder at the same time you create
the trunk/subproject folder. From that point on making a tag for that
project is still a single command.

Or you could re-think your repository structure and use the alternative:
/project/trunk
/project/branches
/project/tags

structure. The flexibility is there to find something that will fit
how you like to work.

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 20:08:59 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.