Sha1 & Out Of Memory Git Push
<p>I have setup a bare repo and have am actively using it via ssh. I've noticed my latest set of commits cannot push to this repo (file size?) but a smaller commit can push to another repo on the same machine.</p>

<p>I have increased some pack parameters to 1024m and ensured there is enough memory available on the remote machine.</p>

<blockquote>
  <p>$ git push
  $ git push warning: push.default is unset; its implicit value has
  changed in Git 2.0 from 'matching' to 'simple'. To squelch this
  message and maintain the traditional behavior, use:</p>
  
  <p>git config --global push.default matching</p>
  
  <p>To squelch this message and adopt the new behavior now, use:</p>
  
  <p>git config --global push.default simple</p>
  
  <p>When push.default is set to 'matching', git will push local branches
  to the remote branches that already exist with the same name.</p>
  
  <p>Since Git 2.0, Git defaults to the more conservative 'simple'
  behavior, which only pushes the current branch to the corresponding
  remote branch that 'git pull' uses to update the current branch.</p>
  
  <p>See 'git help config' and search for 'push.default' for further
  information. (the 'simple' mode was introduced in Git 1.7.11. Use the
  similar mode 'current' instead of 'simple' if you sometimes use older
  versions of Git)</p>
  
  <p>foo@foo's password: Counting objects: 104, done. Compressing
  objects: 100% (100/100), done. fatal: Out of memory, malloc failed
  (tried to allocate 914457600 bytes) fatal: sha1 file '' write
  error: Invalid argument error: failed to push some refs to
  'ssh://foo@foo'</p>
</blockquote>