1. 31 May, 2021 1 commit
  2. 27 May, 2021 1 commit
  3. 19 May, 2021 1 commit
  4. 18 May, 2021 4 commits
  5. 16 May, 2021 5 commits
  6. 13 May, 2021 3 commits
  7. 12 May, 2021 2 commits
  8. 11 May, 2021 4 commits
  9. 06 May, 2021 8 commits
  10. 05 May, 2021 4 commits
  11. 04 May, 2021 2 commits
  12. 02 May, 2021 1 commit
  13. 01 May, 2021 1 commit
  14. 28 Apr, 2021 3 commits
    • repo: validate repository paths · c15ed350
      Ensure that a repository's path (at initialization or open time) is
      valid.  On Windows systems, this means that the longest known path
      beneath the repository will fit within MAX_PATH: this is a lock file for
      a loose object within the repository itself.
      
      Other paths, like a very long loose reference, may fail to be opened
      after the repository is opened.  These variable length paths will be
      checked when they are accessed themselves.  This new functionality is
      done at open to prevent needlessly checking every file in the gitdir
      (eg, `MERGE_HEAD`) for its length when we could instead check once at
      repository open time.
      Edward Thomson committed
    • refs: ensure loose refs adhere to path validation · e5851c62
      On Windows, we need to enforce MAX_PATH for loose references and their
      reflogs.  Ensure that any path - including the lock file - would fit
      within the 260 character maximum.
      
      We do not honor core.longpaths for loose reference files or reflogs.
      core.longpaths only applies to paths in the working directory.
      Edward Thomson committed