title: Subversion revision number across multiple projects
body: <p>When using Subversion (svn) for source control with multiple projects I've noticed that the revision number increases across all of my projects' directories.  To illustrate my svn layout (using fictitious project names): </p>
  
  <pre>
      /NinjaProg/branches
                /tags
                /trunk
      /StealthApp/branches
                 /tags
                 /trunk
      /SnailApp/branches
               /tags
               /trunk
  </pre>
  
  <p>When I perform a commit to the trunk of the Ninja Program, let's say I get that it has been updated to revision 7.  The next day let's say that I make a small change to the Stealth Application and it comes back as revision 8.</p>
  
  <p>The question is this: <strong>Is it common accepted practice to, when maintaining multiple projects with one Subversion server, to have unrelated projects' revision number increase across all projects?</strong> Or am I doing it wrong and should be creating individual repositories for each project?  Or is it something else entirely?</p>
  
  <p><strong>EDIT:</strong> I delayed in flagging an answer because it had become clear that there are reasons for both approaches, and even though this question came first, I'd like to point to some other questions that are ultimately asking the same question: </p>
  
  <p><a href="https://stackoverflow.com/questions/130447/should-i-store-all-projects-in-one-repository-or-mulitiple">Should I store all projects in one repository or mulitiple?</a></p>
  
  <p><a href="https://stackoverflow.com/questions/252459/one-svn-repository-or-many">One SVN Repository or many?</a> </p>