1. 13 Feb, 2015 4 commits
  2. 21 May, 2014 1 commit
  3. 21 Apr, 2014 1 commit
  4. 30 Oct, 2013 1 commit
    • protocol: basic support for multi_ack_detailed · 2f8c481c
      This tells the server that we speak it, but we don't make use of its
      extra information to determine if there's a better place to stop
      negotiating.
      
      In a somewhat-related change, reorder the capabilities so we ask for
      them in the same order as git does.
      
      Also take this opportunity to factor out a fairly-indented portion of
      the negotiation logic.
      Carlos Martín Nieto committed
  5. 04 Oct, 2013 1 commit
  6. 12 Mar, 2013 1 commit
  7. 08 Jan, 2013 1 commit
  8. 29 Nov, 2012 1 commit
  9. 28 Nov, 2012 1 commit
  10. 01 Nov, 2012 1 commit
  11. 30 Sep, 2012 1 commit
  12. 24 Aug, 2012 1 commit
  13. 30 Jul, 2012 2 commits
  14. 13 Jul, 2012 1 commit
    • pkt: correctly advertise capabilitites · 7b8c9e12
      The correct way to advertise out capabilities is by appending them to
      the first 'want' line, using SP as separator, instead of NUL as the
      server does. Inconsistent documentation lead to the use of NUL in
      libgit2.
      
      Fix this so we can request much more efficient packs from the
      remote which reduces the indexing time considerably.
      Carlos Martín Nieto committed
  15. 19 May, 2012 1 commit
  16. 17 May, 2012 2 commits
  17. 08 May, 2012 1 commit
  18. 30 Apr, 2012 2 commits
  19. 28 Apr, 2012 1 commit
  20. 25 Apr, 2012 1 commit
  21. 17 Apr, 2012 1 commit
  22. 11 Apr, 2012 1 commit
  23. 02 Mar, 2012 1 commit
    • Clean up GIT_UNUSED macros on all platforms · 854eccbb
      It turns out that commit 31e9cfc4cbcaf1b38cdd3dbe3282a8f57e5366a5
      did not fix the GIT_USUSED behavior on all platforms.  This commit
      walks through and really cleans things up more thoroughly, getting
      rid of the unnecessary stuff.
      
      To remove the use of some GIT_UNUSED, I ended up adding a couple
      of new iterators for hashtables that allow you to iterator just
      over keys or just over values.
      
      In making this change, I found a bug in the clar tests (where we
      were doing *count++ but meant to do (*count)++ to increment the
      value).  I fixed that but then found the test failing because it
      was not really using an empty repo.  So, I took some of the code
      that I wrote for iterator testing and moved it to clar_helpers.c,
      then made use of that to make it easier to open fixtures on a
      per test basis even within a single test file.
      Russell Belfer committed
  24. 13 Feb, 2012 1 commit
  25. 08 Dec, 2011 1 commit
    • Use git_buf for path storage instead of stack-based buffers · 97769280
      This converts virtually all of the places that allocate GIT_PATH_MAX
      buffers on the stack for manipulating paths to use git_buf objects
      instead.  The patch is pretty careful not to touch the public API
      for libgit2, so there are a few places that still use GIT_PATH_MAX.
      
      This extends and changes some details of the git_buf implementation
      to add a couple of extra functions and to make error handling easier.
      
      This includes serious alterations to all the path.c functions, and
      several of the fileops.c ones, too.  Also, there are a number of new
      functions that parallel existing ones except that use a git_buf
      instead of a stack-based buffer (such as git_config_find_global_r
      that exists alongsize git_config_find_global).
      
      This also modifies the win32 version of p_realpath to allocate whatever
      buffer size is needed to accommodate the realpath instead of hardcoding
      a GIT_PATH_MAX limit, but that change needs to be tested still.
      Russell Belfer committed
  26. 28 Nov, 2011 1 commit
  27. 29 Oct, 2011 1 commit
  28. 12 Oct, 2011 5 commits
  29. 01 Oct, 2011 1 commit
  30. 22 Sep, 2011 1 commit