1. 22 Jan, 2019 1 commit
  2. 01 Dec, 2018 1 commit
  3. 10 Jun, 2018 1 commit
  4. 29 Dec, 2016 1 commit
  5. 22 May, 2015 1 commit
    • branch: error out if we cannot find the remote · 5014fe95
      When we look for which remote corresponds to a remote-tracking branch,
      we look in the refspecs to see which ones matches. If none do, we should
      abort. We currently ignore the error message from this operation, so
      let's not do that anymore.
      
      As part of the test we're writing, let's test for the expected behaviour
      if we cannot find a refspec which tells us what the remote-tracking
      branch for a remote would look like.
      Carlos Martín Nieto committed
  6. 03 Mar, 2015 3 commits
    • config: borrow refcounted references · 9a97f49e
      This changes the get_entry() method to return a refcounted version of
      the config entry, which you have to free when you're done.
      
      This allows us to avoid freeing the memory in which the entry is stored
      on a refresh, which may happen at any time for a live config.
      
      For this reason, get_string() has been forbidden on live configs and a
      new function get_string_buf() has been added, which stores the string in
      a git_buf which the user then owns.
      
      The functions which parse the string value takea advantage of the
      borrowing to parse safely and then release the entry.
      Carlos Martín Nieto committed
    • branch: don't accept a reflog message override · 6bfb990d
      This namespace is about behaving like git's branch command, so let's do
      exactly that instead of taking a reflog message.
      
      This override is still available via the reference namespace.
      Carlos Martín Nieto committed
    • Remove the signature from ref-modifying functions · 659cf202
      The signature for the reflog is not something which changes
      dynamically. Almost all uses will be NULL, since we want for the
      repository's default identity to be used, making it noise.
      
      In order to allow for changing the identity, we instead provide
      git_repository_set_ident() and git_repository_ident() which allow a user
      to override the choice of signature.
      Carlos Martín Nieto committed
  7. 17 Nov, 2014 1 commit
  8. 08 Nov, 2014 1 commit
  9. 30 Jan, 2014 1 commit
  10. 14 Nov, 2013 1 commit
  11. 10 May, 2013 1 commit
  12. 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
  13. 11 Apr, 2013 1 commit
  14. 30 Mar, 2013 1 commit
  15. 10 Dec, 2012 1 commit
  16. 01 Dec, 2012 1 commit
  17. 30 Nov, 2012 1 commit
  18. 28 Nov, 2012 2 commits
  19. 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
  20. 13 Sep, 2012 1 commit
  21. 24 Jul, 2012 1 commit