title: Git: Best strategy to create repos
body: <p>I am new to Git and I am not sure what strategy fits best for my 1st project with it.</p>
  
  <p>e.g.</p>
  
  <pre><code>/src
      /base/forms
      /base//masks
      /base/logics
      /base/communication
      /prj/A
      /prj/B
      /prj/C
  </code></pre>
  
  <p>src is a software. It is in use in 3 projects (A, B, C). Every project is a bit different. But the difference is all handled in the code of /prj/X. The codes of /base are the same.</p>
  
  <p>Now it can be possibe that I need to update a base-module (e.g. forms) but just for prj B. And some weeks later it will be for every prj.</p>
  
  <p>Whats the best way to organize my git?</p>
  
  <p>One big repo with anythink in it (src)?</p>
  
  <p>Or a repo per section (base/prj)?</p>
  
  <p>Or a repo per dir (base/form, base/mask, ... prj/A, prj/B, ...)?</p>
  
  <p>Think to answer I would need a bit of experience with git but as I already said I am new to it.</p>
  
  <p>Thanks for input!</p>