1. 12 Nov, 2015 2 commits
  2. 29 Oct, 2015 1 commit
  3. 28 Oct, 2015 1 commit
  4. 17 Sep, 2015 1 commit
    • git_futils_mkdir_*: make a relative-to-base mkdir · ac2fba0e
      Untangle git_futils_mkdir from git_futils_mkdir_ext - the latter
      assumes that we own everything beneath the base, as if it were
      being called with a base of the repository or working directory,
      and is tailored towards checkout and ensuring that there is no
      bogosity beneath the base that must be cleaned up.
      
      This is (at best) slow and (at worst) unsafe in the larger context
      of a filesystem where we do not own things and cannot do things like
      unlink symlinks that are in our way.
      Edward Thomson committed
  5. 28 Aug, 2015 1 commit
  6. 12 Jul, 2015 1 commit
  7. 08 Mar, 2015 1 commit
  8. 15 Feb, 2015 1 commit
  9. 03 Feb, 2015 1 commit
  10. 16 Dec, 2014 2 commits
    • reference_create: validate loose names · ee5da720
      Validate loose reference names on Win32.
      Edward Thomson committed
    • checkout: disallow bad paths on win32 · a64119e3
      Disallow:
       1. paths with trailing dot
       2. paths with trailing space
       3. paths with trailing colon
       4. paths that are 8.3 short names of .git folders ("GIT~1")
       5. paths that are reserved path names (COM1, LPT1, etc).
       6. paths with reserved DOS characters (colons, asterisks, etc)
      
      These paths would (without \\?\ syntax) be elided to other paths - for
      example, ".git." would be written as ".git".  As a result, writing these
      paths literally (using \\?\ syntax) makes them hard to operate with from
      the shell, Windows Explorer or other tools.  Disallow these.
      Edward Thomson committed
  11. 30 Sep, 2014 1 commit
    • Introduce reference transactions · ab8d9242
      A transaction allows you to lock multiple references and set up changes
      for them before applying the changes all at once (or as close as the
      backend supports).
      
      This can be used for replication purposes, or for making sure some
      operations run when the reference is locked and thus cannot be changed.
      Carlos Martín Nieto committed
  12. 02 Jun, 2014 1 commit
  13. 13 May, 2014 1 commit
  14. 26 Apr, 2014 1 commit
  15. 01 Apr, 2014 1 commit
  16. 20 Mar, 2014 2 commits
  17. 19 Mar, 2014 4 commits
  18. 18 Mar, 2014 1 commit
    • reflog: more comprehensive HEAD tests · bac95e6e
      The existing ones lack checking zeroed ids when switching back from an
      unborn branch as well as what happens when detaching.
      
      The reflog appending function mistakenly wrote zeros when dealing with a
      detached HEAD. This explicitly checks for those situations and fixes
      them.
      Carlos Martín Nieto committed
  19. 17 Mar, 2014 1 commit
  20. 07 Mar, 2014 1 commit
  21. 05 Mar, 2014 1 commit
  22. 10 Feb, 2014 1 commit
  23. 05 Feb, 2014 7 commits
  24. 02 Feb, 2014 1 commit
  25. 01 Feb, 2014 1 commit
  26. 30 Jan, 2014 2 commits
  27. 11 Dec, 2013 1 commit
    • Remove converting user error to GIT_EUSER · 25e0b157
      This changes the behavior of callbacks so that the callback error
      code is not converted into GIT_EUSER and instead we propagate the
      return value through to the caller.  Instead of using the
      giterr_capture and giterr_restore functions, we now rely on all
      functions to pass back the return value from a callback.
      
      To avoid having a return value with no error message, the user
      can call the public giterr_set_str or some such function to set
      an error message.  There is a new helper 'giterr_set_callback'
      that functions can invoke after making a callback which ensures
      that some error message was set in case the callback did not set
      one.
      
      In places where the sign of the callback return value is
      meaningful (e.g. positive to skip, negative to abort), only the
      negative values are returned back to the caller, obviously, since
      the other values allow for continuing the loop.
      
      The hardest parts of this were in the checkout code where positive
      return values were overloaded as meaningful values for checkout.
      I fixed this by adding an output parameter to many of the internal
      checkout functions and removing the overload.  This added some
      code, but it is probably a better implementation.
      
      There is some funkiness in the network code where user provided
      callbacks could be returning a positive or a negative value and
      we want to rely on that to cancel the loop.  There are still a
      couple places where an user error might get turned into GIT_EUSER
      there, I think, though none exercised by the tests.
      Russell Belfer committed