On Wed, Dec 06, 2017 at 08:44:42AM +0100, Bo Berglund wrote:
> It seems like in SVN there must be separate repository folders for
> tags, branches and trunk below each project.
> To me this implies that svn is only able to do these operations at the
> very top of a project tree, is that really so?
> I am coming from CVS(NT) and it was always possible to do the tagging
> and branching for *anything* inside a project tree. For example a
> subtree could be branced and tagged independently from the main
> Is this not possible in SVN?
> If so, how can I convert my CVS repository to SVN correctly, while
> preserving these properties?
> We have used this on many places, for example branching out only a
> single file or two in a directory while leaving the other files on
> Then at a later time when all is checked we merged the changes back
> into TRUNK.
> Is this not possible in svn?
Yes it is.
You could either branch the direct parent folder of the file,
or you could create a new directory somewhere, and copy a file
into this new directory to create a branch of this file.
However, I would suggest you reconsider your workflow, because:
1) There is *no* cost associated with branching the entire tree in SVN.
2) There is *huge* cost for doing the same in CVSNT. And that is the main
reason why your workflow in CVSNT is structured the way it is.
So take a step back and try simply creating *all* your branches at
project-root level. My expectation is that you will not regret it.
Generally, switching version control tools will ultimately always affect
the development process, there is now way around it. It's better to embrace
the advantages and best practices the new tool offers, rather than trying
to shoe-horn existing workflows into the new tool at all costs.
Received on 2017-12-06 11:34:02 CET