title: Git submodule pull request work flow
body: <p>I am curious about some best practices.</p>
  
  <p>There is a git repo that I would like to include as a submodule in my project. I would also like to contribute to this repo and offer pull requests. I have forked the repo and would like to add my fork as the submodule to my project. </p>
  
  <p>I have made a new <code>slim</code> branch in my fork that removes some stuff from the original repo master branch: e.g. example files, demos, etc. I would specifically like to use this <code>slim</code> branch for the submodule to keep the extra stuff out.</p>
  
  <p>I have successfully done this branching and submodule strategy. However I am now wondering about pull requests and contributions to the project. </p>
  
  <p>Ideally I would like to edit the submodule as part of my project, and push commits to the submodules <code>slim</code> branch. I would then like to merge the changes in <code>slim</code> branch back into <code>master</code> so that I can do a pull request. </p>
  
  <p>However I do not want my initial delete commit on the <code>slim</code> branch to be merged back into master. What are some ways I can contribute back to the project with out messing in some of my delete commits?</p>