title: When you clone a repo like Laravel into an existing project do you pull it in as submodule even if you're not planning to contribute?
body: <p>I'm confused on what you do when you've created your own project repo, and then I want to add another repo to it like Laravel 4.  It seems from <a href="http://git-scm.com/book/en/v2/Git-Tools-Submodules" rel="nofollow">Git Pro</a> that submodules might be what I want, and if it is the way to do this will conflict arise with regards to similarly named files like readme.md?  Is this what I'm looking for or is there another solution?</p>
  
  <p>UPDATE:
  Currently I'm cloning <a href="https://github.com/laravel/laravel" rel="nofollow">laravel</a> into my /root, then <strong>deleting the associated .git folder</strong>, then cloning our base installation files that include package.json, bower.json, /docs, /config/, etc etc etc; into my /root, <strong>deleting that .git folder</strong>, then invoking composer install and npm install, running git init, and finally pushing it the projects remote git repo on BitBucket.  The deleting of .git for each cloned repo seems weird (which started this question), so I thought submodules after some searching, but submodules install to subfolders, which I don't want since that doesn't allow for all the CLI to be at a single level, among other things.</p>