Just throwing in my 2 cents: another way to create such "partial
branches" is by performing an "svn copy" with multiple sources
directories (all the ones you want in your branch), all in one commit
directly on the repository. That way, you don't have to delete
anything afterwards (you have only bra
Rob van Oostrum wrote:
"Cleaning up" your branches is a bad idea. It just creates that much
more administrative overhead. Not to mention having to tiptoe around
the deletions when merging the branch back to trunk, which will affect
merge tracking's performance.
What I would do instead is leve
"Cleaning up" your branches is a bad idea. It just creates that much more
administrative overhead. Not to mention having to tiptoe around the
deletions when merging the branch back to trunk, which will affect merge
tracking's performance.
What I would do instead is leverage sparse checkouts to onl
- Original Message
> I understand this is not common workflow, but I'd like to know if there is a
> simple way to accomplish this goal before I start scripting a solution.
>
> Some background: one of the requirements for my organization moving to
> subversion was the ability to create
Hi All,
I understand this is not common workflow, but I'd like to know if
there is a simple way to accomplish this goal before I start scripting a
solution.
Some background: one of the requirements for my organization moving to
subversion was the ability to create tags/branches that contai
