1. 17 Jun, 2013 1 commit
  2. 15 May, 2013 1 commit
  3. 11 May, 2013 1 commit
  4. 10 May, 2013 1 commit
  5. 06 May, 2013 1 commit
    • git_branch_set_upstream with local branches · 3d42e9a3
      Currently git_branch_set_upstream when passed a local branch
      creates invalid configuration, for ex. if we setup branch
      'tracking_master' to track local 'master' libgit2 generates
      the following config
      
      ```
      [branch "track_master"]
        remote = .
        merge = .refs/heads/track_master
      ```
      
      The merge value is invalid and calling git_branch_upstream on
      'tracking_master' results in invalid reference error.
      
      It should do:
      
      ```
      [branch "track_master"]
        remote = .
        merge = refs/heads/master
      ```
      Nikolai Vladimirov committed
  6. 01 May, 2013 1 commit
  7. 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
  8. 11 Apr, 2013 1 commit
  9. 31 Mar, 2013 1 commit
  10. 30 Mar, 2013 1 commit
  11. 07 Mar, 2013 1 commit
  12. 26 Feb, 2013 1 commit
  13. 22 Feb, 2013 2 commits
  14. 11 Feb, 2013 1 commit
  15. 05 Feb, 2013 1 commit
  16. 25 Jan, 2013 2 commits
  17. 16 Jan, 2013 1 commit
  18. 10 Dec, 2012 1 commit
  19. 01 Dec, 2012 2 commits
  20. 30 Nov, 2012 1 commit
  21. 28 Nov, 2012 2 commits
  22. 27 Nov, 2012 3 commits
  23. 23 Nov, 2012 1 commit
    • Reset all static variables to NULL in clar's __cleanup · 9094d30b
      Without this change, any failed assertion in the second (or a later) test
      inside a test suite has a chance of double deleting memory, resulting in
      a heap corruption. See #1096 for details.
      
      This leaves alone the test cases where we "just" use cl_git_sandbox_init()
      and cl_git_sandbox_cleanup(). These methods already take good care to not
      double delete a repository.
      
      Fixes #1096
      Sascha Cunz committed
  24. 11 Nov, 2012 1 commit
  25. 25 Oct, 2012 2 commits
  26. 20 Oct, 2012 2 commits
  27. 19 Oct, 2012 2 commits
  28. 11 Oct, 2012 2 commits
  29. 07 Oct, 2012 1 commit