title: Are nested trunk/branches/tags acceptable?
body: <p>In a recent embedded project, we have used the following svn structure:</p>
  
  <pre><code>project
      branches
      tags
      trunk
          electronics
          software
              branches
              tags
              trunk
  </code></pre>
  
  <p>As you can see, there is a nested branches/tags/trunk directory for the software part. This was quite practical for software devs as they could just work there without worrying about the rest.</p>
  
  <p>However it doesn't look <em>right</em> to me, it could be confusing because of the multiple levels of branching, and people working higher in the hierarchy may be inconvenienced by all the garbage they have to download if they checkout the top trunk...</p>
  
  <p>So I am thinking of going for a 1-trunk-only repository for the next project, and if developers don't want the non-software stuff, they can just checkout <code>project/trunk/software</code> and branch to <code>project/branches/br-1234/software</code>, etc.</p>
  
  <p>What do you think about nested trunks? Pros&amp;cons please!</p>
  
  <p>As a side question: Should branches/tags always be copies of the trunk (or another branch), or is it acceptable to make a branch of a sub-directory of trunk?</p>