1. 18 May, 2014 1 commit
  2. 29 Apr, 2014 1 commit
    • commit: safer commit creation with reference update · 217c029b
      The current version of the commit creation and amend function are unsafe
      to use when passing the update_ref parameter, as they do not check that
      the reference at the moment of update points to what the user expects.
      
      Make sure that we're moving history forward when we ask the library to
      update the reference for us by checking that the first parent of the new
      commit is the current value of the reference. We also make sure that the
      ref we're updating hasn't moved between the read and the write.
      
      Similarly, when amending a commit, make sure that the current tip of the
      branch is the commit we're amending.
      Carlos Martín Nieto committed
  3. 08 Feb, 2014 1 commit
    • Add git_commit_amend API · 80c29fe9
      This adds an API to amend an existing commit, basically a shorthand
      for creating a new commit filling in missing parameters from the
      values of an existing commit.  As part of this, I also added a new
      "sys" API to create a commit using a callback to get the parents.
      This allowed me to rewrite all the other commit creation APIs so
      that temporary allocations are no longer needed.
      Russell Belfer committed
  4. 27 Jan, 2014 1 commit
  5. 25 Jan, 2014 1 commit
  6. 14 Nov, 2013 1 commit
  7. 12 Jan, 2013 1 commit
  8. 27 Nov, 2012 1 commit
  9. 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
  10. 01 Nov, 2012 1 commit
  11. 30 Oct, 2012 1 commit
  12. 26 Oct, 2012 1 commit
  13. 14 Aug, 2012 1 commit
    • Make git_message_prettify return bytes written · 85a0e28b
      If you want to be absolutely safe with git_message_prettify, you
      can now pass a NULL pointer for the buffer and get back the number
      of bytes that would be copied into the buffer.
      
      This means that an error is a non-negative return code and a
      success will be greater than zero from this function.
      Russell Belfer committed
  14. 12 Aug, 2012 1 commit
  15. 19 Jun, 2012 1 commit
  16. 15 Jun, 2012 1 commit
  17. 07 May, 2012 1 commit
  18. 05 May, 2012 1 commit
  19. 25 Jan, 2012 1 commit
  20. 05 Jan, 2012 1 commit
  21. 02 Jan, 2012 1 commit
  22. 18 Dec, 2011 1 commit
  23. 14 Dec, 2011 1 commit