1. 10 Jun, 2019 2 commits
  2. 24 May, 2019 1 commit
  3. 24 Jan, 2019 1 commit
    • index: preserve extension parsing errors · 0bf7e043
      Previously, we would clobber any extension-specific error message with
      an "extension is truncated" message. This makes `read_extension`
      correctly preserve those errors, takes responsibility for truncation
      errors, and adds a new message with the actual extension signature for
      unsupported mandatory extensions.
      Etienne Samson committed
  4. 15 Jan, 2019 1 commit
  5. 14 Jan, 2019 1 commit
  6. 04 Dec, 2018 3 commits
  7. 03 Dec, 2018 1 commit
    • crlf_data: move to a "to_workdir" folder · 13a8bc92
      Move the crlf_data folders reponsible for holding the state of the
      filters going into the working directory to "to_workdir" variations of
      the folder name to accommodate future growth into the "to odb" filter
      variation.  Update the script to create these new folders as appopriate.
      Edward Thomson committed
  8. 05 Nov, 2018 1 commit
  9. 20 Oct, 2018 1 commit
    • checkout: fix test fixture missing objects · c79e6081
      The testrepo test fixture has an index file that's damaged, missing an
      object.  The index previously had an entry of `src/index.c` with id
      3161df8cbf3a006b4ef85be6497a0ea6bde98541, but that object was missing in
      the repository.  This commit adds an object to the repository and
      updates the index to use that existing blob.
      
      Similarly, the index has an entry for `readme` with an id of
      97328ac7e3bd0bcd3900cb3e7a624d71dd0df888.  This can be restored from
      other test repositories.
      
      With these fixed, now the write tree from index tests can pass since they
      validate object existence.
      Edward Thomson committed
  10. 04 Oct, 2018 1 commit
    • tests: verify diff stats with renames in subdirectory · 3148efd2
      Until now, we didn't have any tests that verified that our format for
      renames in subdirectories is correct. While our current behaviour is no
      different than for renames that do not happen with a common prefix
      shared between old and new file name, we intend to change the format to
      instead match the format that upstream git uses.
      
      Add a test case for this to document our current behaviour and to show
      how the next commit will change that format.
      Patrick Steinhardt committed
  11. 14 Aug, 2018 1 commit
  12. 18 Jul, 2018 1 commit
    • tree: accept null ids in existing trees when updating · 2dff7e28
      When we add entries to a treebuilder we validate them. But we validate even
      those that we're adding because they exist in the base tree. This disables
      using the normal mechanisms on these trees, even to fix them.
      
      Keep track of whether the entry we're appending comes from an existing tree and
      bypass the name and id validation if it's from existing data.
      Carlos Martín Nieto committed
  13. 15 Jun, 2018 3 commits
  14. 22 May, 2018 1 commit
  15. 17 Apr, 2018 3 commits
  16. 12 Apr, 2018 1 commit
    • revwalk: fix uninteresting revs sometimes not limiting graphwalk · 54fd80e3
      When we want to limit our graphwalk, we use the heuristic of checking
      whether the newest limiting (uninteresting) revision is newer than the
      oldest interesting revision. We do so by inspecting whether the first
      item's commit time of the user-supplied list of revisions is newer than
      the last added interesting revision. This is wrong though, as the user
      supplied list is in no way guaranteed to be sorted by increasing commit
      dates. This could lead us to abort the revwalk early before applying all
      relevant limiting revisions, outputting revisions which should in fact
      have been hidden.
      
      Fix the heuristic by instead checking whether _any_ of the limiting
      commits was made earlier than the last interesting commit. Add a test.
      Patrick Steinhardt committed
  17. 24 Feb, 2018 1 commit
  18. 20 Feb, 2018 1 commit
  19. 04 Feb, 2018 2 commits
  20. 04 Dec, 2017 1 commit
  21. 25 Aug, 2017 1 commit
    • submodule: refuse lookup in bare repositories · 477b3e04
      While it is technically possible to look up submodules inside of a
      bare repository by reading the submodule configuration of a specific
      commit, we do not offer this functionality right now. As such, calling
      both `git_submodule_lookup` and `git_submodule_foreach` should error out
      early when these functions encounter a bare repository. While
      `git_submodule_lookup` already does return an error due to not being
      able to parse the configuration, `git_submodule_foreach` simply returns
      success and never invokes the callback function.
      
      Fix the issue by having both functions check whether the repository is
      bare and returning an error in that case.
      Patrick Steinhardt committed
  22. 25 Jul, 2017 1 commit
  23. 20 Jul, 2017 1 commit
  24. 06 Jun, 2017 1 commit
  25. 17 Mar, 2017 1 commit
    • submodule: resolve URLs relative to main worktree · b0c9bc92
      It is possible to specify submodule URLs relative to the repository
      location. E.g. having a submodule with URL "../submodule" will look for
      the submodule at "repo/../submodule".
      
      With the introduction of worktrees, though, we cannot simply resolve the
      URL relative to the repository location itself. If the repository for
      which a URL is to be resolved is a working tree, we have to resolve the
      URL relative to the parent's repository path. Otherwise, the URL would
      change depending on where the working tree is located.
      
      Fix this by special-casing when we have a working tree while getting the
      URL base.
      Patrick Steinhardt committed
  26. 03 Mar, 2017 2 commits
  27. 13 Feb, 2017 4 commits
  28. 09 Feb, 2017 1 commit