Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>We do this at our company and have had a lot of success. </p> <p>We have 3 top level directories:</p> <ul> <li>tags</li> <li>branches</li> <li>trunk</li> </ul> <p>And then we have each project as a sub-directory of those.</p> <p>We still branch at the project level though and still use svn:externals. But if we had a smaller source tree we would branch at the trunk level and not use svn:extenrals. </p> <p>It's nice to be able to have all projects' trunk at the same place. You can back it up, you can check it all out and you have all the most recent stuff together. You don't lose the single location for all branches nor single location for all tags either because they are all in subdirectories of /branches/projectX and /tags/projectX </p> <p><strong>Problems with svn:externals:</strong></p> <p>If your projects are not extermely HUGE then you could just branch the whole trunk each time and avoid all of the problems with svn:externals.</p> <p>The problem with svn:externals is that when you make a branch, it doesn't automatically create a branch for each of the svn:externals for you. This is a problem because then over time all of your old branches won't be able to compile as your trunk gets more updated. Another problem is that if you make a fix in any branch to an svn:external, all your other branches break.</p> <p>Another problem with svn externals is that when you do an svn:log at the root level, you don't see any changes from svn externals. </p> <p>Hopefully one day svn externals will be fixed to address the above problems, but until that day branching and svn:externals is an absolute nightmare. </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload