1. 30 Dec, 2014 1 commit
  2. 06 Dec, 2014 1 commit
  3. 09 Nov, 2014 1 commit
    • push: use the common refspec parser · aad638f3
      There is one well-known and well-tested parser which we should use,
      instead of implementing parsing a second time.
      
      The common parser is also augmented to copy the LHS into the RHS if the
      latter is empty.
      
      The expressions test had to change a bit, as we now catch a bad RHS of a
      refspec locally.
      Carlos Martín Nieto committed
  4. 08 Nov, 2014 2 commits
  5. 30 Sep, 2014 1 commit
  6. 31 Aug, 2014 1 commit
  7. 15 Aug, 2014 1 commit
  8. 14 Aug, 2014 1 commit
  9. 26 Jun, 2014 1 commit
  10. 21 Apr, 2014 1 commit
  11. 02 Apr, 2014 1 commit
  12. 05 Feb, 2014 3 commits
  13. 27 Jan, 2014 1 commit
  14. 12 Dec, 2013 1 commit
  15. 18 Nov, 2013 1 commit
  16. 14 Nov, 2013 1 commit
  17. 11 Nov, 2013 2 commits
  18. 08 Nov, 2013 1 commit
  19. 07 Nov, 2013 1 commit
  20. 05 Nov, 2013 2 commits
  21. 25 Oct, 2013 1 commit
  22. 23 Oct, 2013 1 commit
  23. 21 Oct, 2013 1 commit
  24. 03 Oct, 2013 2 commits
  25. 02 Oct, 2013 4 commits
  26. 30 Sep, 2013 1 commit
    • Initial Implementation of progress reports during push · b176eded
      This adds the basics of progress reporting during push. While progress
      for all aspects of a push operation are not reported with this change,
      it lays the foundation to add these later. Push progress reporting
      can be improved in the future - and consumers of the API should
      just get more accurate information at that point.
      
      The main areas where this is lacking are:
      
      1) packbuilding progress: does not report progress during deltafication,
         as this involves coordinating progress from multiple threads.
      
      2) network progress: reports progress as objects and bytes are going
         to be written to the subtransport (instead of as client gets
         confirmation that they have been received by the server) and leaves
         out some of the bytes that are transfered as part of the push protocol.
         Basically, this reports the pack bytes that are written to the
         subtransport. It does not report the bytes sent on the wire that
         are received by the server. This should be a good estimate of
         progress (and an improvement over no progress).
      Jameson Miller committed
  27. 14 Aug, 2013 1 commit
    • Test SSH in travis · 5be622fb
      Set up the ssh credentials so we are able to talk to localhost and
      issue git commands. Move to use a script, as the command list is
      getting somewhat long.
      
      While here, delay installing valgrind until we need it, as it and its
      dependencies are by far the largest downloads and this allows us to
      start compiling (and failing) faster and we only incur this cost when
      the test suite runs successfully.
      Carlos Martín Nieto committed
  28. 12 Jul, 2013 1 commit
  29. 20 Apr, 2013 1 commit
    • remote: handle multiple refspecs · 4330ab26
      A remote can have a multitude of refspecs. Up to now our git_remote's
      have supported a single one for each fetch and push out of simplicity
      to get something working.
      
      Let the remotes and internal code know about multiple remotes and get
      the tests passing with them.
      
      Instead of setting a refspec, the external users can clear all and add
      refspecs. This should be enough for most uses, though we're still
      missing a querying function.
      Carlos Martín Nieto committed
  30. 11 Feb, 2013 1 commit
  31. 31 Jan, 2013 1 commit