1. 12 Jun, 2015 1 commit
  2. 13 May, 2015 2 commits
    • remote: remove live changing of refspecs · 77254990
      The base refspecs changing can be a cause of confusion as to what is the
      current base refspec set and complicate saving the remote's
      configuration.
      
      Change `git_remote_add_{fetch,push}()` to update the configuration
      instead of an instance.
      
      This finally makes `git_remote_save()` a no-op, it will be removed in a
      later commit.
      Carlos Martín Nieto committed
    • Remove the callbacks struct from the remote · 8f0104ec
      Having the setting be different from calling its actions was not a great
      idea and made for the sake of the wrong convenience.
      
      Instead of that, accept either fetch options, push options or the
      callbacks when dealing with the remote. The fetch options are currently
      only the callbacks, but more options will be moved from setters and
      getters on the remote to the options.
      
      This does mean passing the same struct along the different functions but
      the typical use-case will only call git_remote_fetch() or
      git_remote_push() and so won't notice much difference.
      Carlos Martín Nieto committed
  3. 03 Mar, 2015 2 commits
  4. 30 Dec, 2014 1 commit
  5. 06 Dec, 2014 1 commit
  6. 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
  7. 08 Nov, 2014 2 commits
  8. 30 Sep, 2014 1 commit
  9. 31 Aug, 2014 1 commit
  10. 15 Aug, 2014 1 commit
  11. 14 Aug, 2014 1 commit
  12. 26 Jun, 2014 1 commit
  13. 21 Apr, 2014 1 commit
  14. 02 Apr, 2014 1 commit
  15. 05 Feb, 2014 3 commits
  16. 27 Jan, 2014 1 commit
  17. 12 Dec, 2013 1 commit
  18. 18 Nov, 2013 1 commit
  19. 14 Nov, 2013 1 commit
  20. 11 Nov, 2013 2 commits
  21. 08 Nov, 2013 1 commit
  22. 07 Nov, 2013 1 commit
  23. 05 Nov, 2013 2 commits
  24. 25 Oct, 2013 1 commit
  25. 23 Oct, 2013 1 commit
  26. 21 Oct, 2013 1 commit
  27. 03 Oct, 2013 2 commits
  28. 02 Oct, 2013 4 commits
  29. 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