1. 12 Nov, 2017 1 commit
    • signature: distinguish +0000 and -0000 UTC offsets · f063dafb
      Git considers '-0000' a valid offset for signature lines.  They need to
      be treated as _not_ equal to a '+0000' signature offset.  Parsing a
      signature line stores the offset in a signed integer which does not
      distinguish between `+0` and `-0`.
      
      This patch adds an additional flag `sign` to the `git_time` in the
      `signature` object which is populated with the sign of the offset.  In
      addition to exposing this information to the user, this information is
      also used to compare signatures.
      
      /cc @pks-t @ethomson
      Henry Kleynhans committed
  2. 04 May, 2016 1 commit
    • Fix initial commit test · 5785ae9b
      `test_commit_commit__create_initial_commit_parent_not_current` was not correctly 
      testing that `HEAD` was not changed. Now we grab the oid that it was pointing to
      before the call to `git_commit_create` and the oid that it's pointing to afterwards
      and compare those.
      John Haley committed
  3. 03 May, 2016 1 commit
  4. 28 Apr, 2016 1 commit
  5. 17 Mar, 2016 1 commit
  6. 15 Mar, 2016 1 commit
  7. 08 Mar, 2016 1 commit
  8. 28 Feb, 2016 2 commits
  9. 16 Feb, 2016 1 commit
  10. 11 Feb, 2016 1 commit
    • commit: don't forget the last header field · 460ae11f
      When we moved the logic to handle the first one, wrong loop logic was
      kept in place which meant we still finished early. But we now notice it
      because we're not reading past the last LF we find.
      
      This was not noticed before as the last field in the tested commit was
      multi-line which does not trigger the early break.
      Carlos Martín Nieto committed
  11. 09 Feb, 2016 2 commits
  12. 17 Dec, 2015 1 commit
  13. 01 Dec, 2015 1 commit
  14. 03 Nov, 2015 1 commit
  15. 21 Oct, 2015 1 commit
  16. 22 Jun, 2015 1 commit
  17. 11 Jun, 2015 1 commit
    • commit: ignore multiple author fields · 65d69fe8
      Some tools create multiple author fields. git is rather lax when parsing
      them, although fsck does complain about them. This means that they exist
      in the wild.
      
      As it's not too taxing to check for them, and there shouldn't be a
      noticeable slowdown when dealing with correct commits, add logic to skip
      over these extra fields when parsing the commit.
      Carlos Martín Nieto committed
  18. 03 Mar, 2015 1 commit
    • 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
  19. 10 Sep, 2014 1 commit
  20. 01 Jul, 2014 1 commit
  21. 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
  22. 04 Feb, 2014 1 commit
  23. 22 Jan, 2014 1 commit
  24. 15 Jan, 2014 1 commit
  25. 02 Dec, 2013 1 commit
  26. 14 Nov, 2013 1 commit