----- Original Message -----
From: "Jens Vonderheide" <vonderheide@redlink.de>
> I plan to use subversion with a software that is currently under CVS
control.
> With CVS, I created a branch after each release and used this branch for
> bugfixes and the trunk for new development. Is this method recommended for
> subversion as well? And can I assign a sort of symbolic name to this
> branch so that the branch name itself is different for each release (e.g.
> "release-030919"), but the most recent release is also available as
> "release"?
Sure you can do that with subversion. It's just a little different than with
CVS.
If you create a repository for each project, then add the following folders
to it with your first import:
/trunk/
/branches/
/tags/
Now import your files to /trunk/. That's where you're working on.
If you now create a branch just make a "copy" from trunk
to /branches/branchname/
That's where you can work on too. But if you want to make a "release"
then make a copy to /tags/release-x.x.x/.
Just make sure that you don't commit changes to the tags folder.
> Some files are used in more than one project. If I put all these projects
> into the same repository, is there a way to link these files togehter so
> that a change to one position of this file is duplicated in all other?
check the book for "svn:externals" about that.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Sep 20 19:22:51 2003