title: How to fix 'gitmodulesPath: disallowed submodule path' on 'git fsck'
body: <p>I have a very old git project, and i did a <code>git fsck</code> on it.
  I am receiving the following output:</p>
  
  <pre><code>git fsck --full
  Prüfe Objekt-Verzeichnisse: 100% (256/256), Fertig.
  Prüfe Objekte: 100% (35666/35666), Fertig.
  error in blob 5ac33d03cc28290156dcd17cf8a4efd95adee7b9: gitmodulesPath: disallowed submodule path: --force
  dangling blob dc3821dca2a21a6253c929915011e5b1be932203
  </code></pre>
  
  <p>After some digging in the current state I also checked the history of the <code>.gitmodules</code> file because the current version did not have an error.</p>
  
  <p>I found a commit more than a year ago that has the following <code>.gitmodules</code> content:</p>
  
  <pre><code>[submodule "--force"]
      path = --force
      url = git@gitlab.mygitserver.com:mygroup/myproject.git
  </code></pre>
  
  <p>in the next commit this submodule was deleted again. so somebody clearly was trying something out how submodules work. the problem is now, that it is in the project history.</p>
  
  <p>Is <code>git fsck</code> really checking every <code>.gitmodules</code> file in history if it had errors at any time?
  And how can i fix this?</p>