1. 22 Jan, 2019 1 commit
  2. 04 Dec, 2018 1 commit
    • Additional core.autocrlf and core.safecrlf tests · 2a9b0102
      This is a cherry-pick of the tests from the following commits:
      
      core.autocrlf=true and core.safecrlf=true did not fail on LF-only file as vanilla git does
      Adding a CRLF-file with core.autocrlf=input and core.safecrlf=true does not fail as with vanilla git
      Make files with #CR!=#CRLF not fail with core.safecrlf=true
      
      Reported-by: Yue Lin Ho <b8732003@student.nsysu.edu.tw>
      Signed-off-by: Sven Strickroth <email@cs-ware.de>
      Sven Strickroth committed
  3. 01 Dec, 2018 1 commit
  4. 10 Jun, 2018 1 commit
  5. 07 Apr, 2017 1 commit
    • filter: only close filter if it's been initialized correctly · cf07db2f
      In the function `git_filter_list_stream_data`, we initialize, write and
      subesquently close the stream which should receive content processed by
      the filter. While we skip writing to the stream if its initialization
      failed, we still try to close it unconditionally -- even if the
      initialization failed, where the stream might not be set at all, leading
      us to segfault.
      
      Semantics in this code is not really clear. The function handling the
      same logic for files instead of data seems to do the right thing here in
      only closing the stream when initialization succeeded. When stepping
      back a bit, this is only reasonable: if a stream cannot be initialized,
      the caller would not expect it to be closed again. So actually, both
      callers of `stream_list_init` fail to do so. The data streaming function
      will always close the stream and the file streaming function will not
      close the stream if writing to it has failed.
      
      The fix is thus two-fold:
      
      - callers of `stream_list_init` now close the stream iff it has been
        initialized
      - `stream_list_init` now closes the lastly initialized stream if
        the current stream in the chain failed to initialize
      
      Add a test which segfaulted previous to these changes.
      Patrick Steinhardt committed
  6. 10 Jul, 2015 2 commits
  7. 02 Jul, 2015 2 commits
  8. 01 Jul, 2015 1 commit
  9. 29 Jun, 2015 1 commit
  10. 22 Jun, 2015 1 commit
  11. 10 Jun, 2015 1 commit
  12. 26 May, 2015 1 commit
  13. 24 Mar, 2015 1 commit
  14. 06 Mar, 2015 1 commit
  15. 19 Feb, 2015 2 commits
  16. 18 Feb, 2015 2 commits
  17. 17 Feb, 2015 1 commit
  18. 20 Jan, 2015 1 commit
  19. 30 May, 2014 1 commit
  20. 19 May, 2014 1 commit
  21. 06 May, 2014 1 commit
    • Add filter options and ALLOW_UNSAFE · 5269008c
      Diff and status do not want core.safecrlf to actually raise an
      error regardless of the setting, so this extends the filter API
      with an additional options flags parameter and adds a flag so that
      filters can be applied with GIT_FILTER_OPT_ALLOW_UNSAFE, indicating
      that unsafe filter application should be downgraded from a failure
      to a warning.
      Russell Belfer committed
  22. 08 Apr, 2014 1 commit
  23. 12 Feb, 2014 1 commit
  24. 25 Jan, 2014 1 commit
  25. 08 Jan, 2014 1 commit
  26. 14 Nov, 2013 1 commit