1. 21 Jan, 2017 1 commit
  2. 14 Jan, 2017 1 commit
  3. 03 Jan, 2017 2 commits
  4. 15 Nov, 2016 1 commit
  5. 14 Nov, 2016 1 commit
  6. 09 Oct, 2016 2 commits
  7. 06 Oct, 2016 1 commit
  8. 10 Aug, 2016 1 commit
    • index: support index v4 · 5625d86b
      Support reading and writing index v4.  Index v4 uses a very simple
      compression scheme for pathnames, but is otherwise similar to index v3.
      
      Signed-off-by: David Turner <dturner@twitter.com>
      David Turner committed
  9. 06 Aug, 2016 1 commit
  10. 04 Aug, 2016 1 commit
  11. 03 Aug, 2016 1 commit
  12. 24 Jul, 2016 1 commit
  13. 15 Jul, 2016 1 commit
    • remote: Handle missing config values when deleting a remote · d81cb2e4
      Somehow I ended up with the following in my ~/.gitconfig:
      [branch "master"]
      remote = origin
      merge = master
      rebase = true
      
      I assume something went crazy while I was running the git.git tests
      some time ago, and that I never noticed until now.
      
      This is not a good configuration, but it shouldn't cause problems. But
      it does. Specifically, if you have this in your config, and you
      perform the following set of actions:
      
      create a remote
      fetch from that remote
      create a branch off of the remote master branch called "master"
      delete the branch
      delete the remote
      
      The remote delete fails with the message "Could not find key
      'branch.master.rebase' to delete". This is because it's iterating over
      the config entries (including the ones in the global config) and
      believes that there is a master branch which must therefore have these
      config keys.
      
      https://github.com/libgit2/libgit2/issues/3856
      David Turner committed
  14. 05 Jul, 2016 1 commit
  15. 30 Jun, 2016 2 commits
  16. 22 Mar, 2016 2 commits
  17. 18 Mar, 2016 1 commit
  18. 17 Mar, 2016 1 commit
  19. 08 Mar, 2016 1 commit
  20. 03 Mar, 2016 2 commits
  21. 28 Feb, 2016 1 commit
  22. 22 Feb, 2016 1 commit
  23. 19 Feb, 2016 1 commit
  24. 09 Dec, 2015 1 commit
  25. 06 Dec, 2015 1 commit
  26. 25 Nov, 2015 1 commit
  27. 12 Nov, 2015 2 commits
  28. 03 Nov, 2015 1 commit
  29. 02 Nov, 2015 1 commit
  30. 08 Sep, 2015 1 commit
    • git_index_add: allow case changing renames · a32bc85e
      On case insensitive platforms, allow `git_index_add` to provide a new
      path for an existing index entry.  Previously, we would maintain the
      case in an index entry without the ability to change it (except by
      removing an entry and re-adding it.)
      
      Higher-level functions (like `git_index_add_bypath` and
      `git_index_add_frombuffers`) continue to keep the old path for easier
      usage.
      Edward Thomson committed
  31. 05 Sep, 2015 1 commit
  32. 26 Aug, 2015 1 commit
  33. 12 Aug, 2015 2 commits