1. 22 Jan, 2019 1 commit
  2. 10 Jun, 2018 1 commit
  3. 13 May, 2015 1 commit
    • 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
  4. 27 Jan, 2014 1 commit
  5. 14 Nov, 2013 1 commit
  6. 08 Nov, 2013 1 commit
  7. 07 Nov, 2013 1 commit
  8. 01 May, 2013 1 commit
  9. 20 Apr, 2013 2 commits
    • remote: allow querying for refspecs · bc6374ea
      Introduce git_remote_{fetch,push}_refspecs() to get a list of refspecs
      from the remote and rename the refspec-adding functions to a less
      silly name.
      
      Use this instead of the vector index hacks in the tests.
      Carlos Martín Nieto committed
    • 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
  10. 31 Mar, 2013 1 commit
  11. 26 Feb, 2013 1 commit
  12. 22 Feb, 2013 2 commits
  13. 11 Feb, 2013 1 commit