1. 16 Mar, 2015 2 commits
  2. 13 Mar, 2015 3 commits
  3. 12 Mar, 2015 1 commit
  4. 11 Mar, 2015 1 commit
    • local: create pack with multiple threads · 0ef54a63
      The default behaviour for the packbuilder is to perform the work in a
      single thread, which is fine for the public API, but we currently have
      no way for a user to determine the number of threads to use when
      creating the packfile, which makes our clone behaviour over the
      filesystem quite a bit slower than what git offers.
      
      This is a very particular scenario, in which we avoid spawning git by
      being ourselves the server-side, so it's probably ok to auto-set the
      threading, as the upload-pack process would do if we were talking to
      git.
      Carlos Martín Nieto committed
  5. 10 Mar, 2015 2 commits
  6. 08 Mar, 2015 2 commits
  7. 06 Mar, 2015 5 commits
  8. 04 Mar, 2015 7 commits
  9. 03 Mar, 2015 13 commits
  10. 02 Mar, 2015 4 commits