title: Gerrit code review of git repo with submodules? Create a dependancy relationship in Gerrit?
body: <p>New with Git but have a background with Mercurial. Not sure if that helps here...</p>
  
  <p>We have a git design repo with submodules used across a number of other designs. 
  Their are users making changes in both the parent module and a submodule as a code update release. </p>
  
  <p>We have methodology to in place to make sure submodule commits are done correctly to keep the parent module pointing to the correct change in the submodule.</p>
  
  <p>The problem is when pushing the commits (parent module and submodule) to Gerrit (using git push origin HEAD:refs/for/$branch) for review we end up with two reviews. One for the parent module, and one for the submodule.</p>
  
  <p>The parent module shows all it's file diffs/patch and then a reference to a change in the submodule with the change hash for the patch but nothing about the files that where modified there.</p>
  
  <p>Is there a way to tie a dependency on the submodule change with the parent module change in Gerrit?  Insure that the parent module change review cannot be submitted/pushed unless the submodule change has also been reviewed ?</p>
  
  <p>Thanks!
  Mick</p>