1. 03 Apr, 2014 1 commit
  2. 17 Mar, 2014 1 commit
  3. 07 Mar, 2014 1 commit
  4. 27 Feb, 2014 1 commit
  5. 30 Jan, 2014 6 commits
  6. 27 Jan, 2014 2 commits
  7. 15 Jan, 2014 1 commit
  8. 13 Jan, 2014 1 commit
  9. 11 Dec, 2013 1 commit
    • Improve GIT_EUSER handling · 96869a4e
      This adds giterr_user_cancel to return GIT_EUSER and clear any
      error message that is sitting around.  As a result of using that
      in places, we need to be more thorough with capturing errors that
      happen inside a callback when used internally.  To help with that,
      this also adds giterr_capture and giterr_restore so that when we
      internally use a foreach-type function that clears errors and
      converts them to GIT_EUSER, it is easier to restore not just the
      return value, but the actual error message text.
      Russell Belfer committed
  10. 05 Nov, 2013 2 commits
  11. 17 Sep, 2013 1 commit
    • No such thing as an orphan branch · 605da51a
      Unfortunately git-core uses the term "unborn branch" and "orphan
      branch" interchangeably. However, "orphan" is only really there for
      the checkout command, which has the `--orphan` option so it doesn't
      actually create the branch.
      
      Branches never have parents, so the distinction of a branch with no
      parents is odd to begin with. Crucially, the error messages deal with
      unborn branches, so let's use that.
      Carlos Martín Nieto committed
  12. 17 Jun, 2013 2 commits
  13. 30 May, 2013 1 commit
  14. 28 May, 2013 1 commit
  15. 11 May, 2013 2 commits
  16. 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
  17. 01 May, 2013 1 commit
  18. 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
  19. 18 Apr, 2013 1 commit
  20. 11 Apr, 2013 1 commit
  21. 31 Mar, 2013 1 commit
  22. 30 Mar, 2013 1 commit
  23. 17 Mar, 2013 1 commit
  24. 07 Mar, 2013 1 commit
  25. 22 Feb, 2013 1 commit
  26. 11 Feb, 2013 1 commit
  27. 05 Feb, 2013 1 commit
  28. 25 Jan, 2013 1 commit
    • Added git_branch_name(). · c253056d
      This is a convenience function to get the branch name of a given
      ref. The returned branch name is compatible with the name that can
      be supplied e.g. to git_branch_lookup(). That is, the prefixes
      "refs/heads" or "refs/remotes" are omitted.
      
      Also added a new test for testing the new function.
      Sebastian Bauer committed
  29. 16 Jan, 2013 2 commits
  30. 08 Jan, 2013 1 commit