Alexis Huxley <ahuxley@gmx.net> writes:
> Hi Subversion People
>
> On the list I saw someone mention this:
>
> svn cp -r 1000 /trunk /tags/foobar-1.0
>
> as a way to tag releases.
>
> And it raised a couple of questions for me, who's jumping
> direct from RCS to SVN without passing through CVS.
>
> At the moment (while SVN lacks module support) I have my various
> programs all stored directly under my SVN root like this:
>
> \__ prog1 __ src
> | \__ lib
> \__ prog2 __ src
> | \__ lib
> \__ prog3 __ src
> \__ lib
>
> So, should I rearrange my sources to be stored under /trunk like this,
> so that I can later make tags with the command line above?:
>
> \__ prog1 __ trunk __ src
> | | \__ lib
> | \__ tags
> \__ prog2 __ trunk __ src
> | | \__ lib
> | \__ tags
> \__ prog3 __ trunk __ src
> | | \__ lib
> | \__ tags
Well, you don't *have* to do so. Instead of using the following
layout:
/proj1
/proj1/trunk
/proj1/tags
/proj2
/proj2/trunk
/proj2/tags
/proj3
/proj3/trunk
/proj3/tags
You could do (if it makes life simpler for you):
/trunk
/trunk/proj1
/trunk/proj2
/trunk/proj3
/tags
/tags/proj1
/tags/proj2
/tags/proj3
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 24 17:32:13 2002