Mirror the changes from patch to git apply, in the manual and master_…

…changes.md

doc/pages/Manual.md

@@ -888,10 +888,11 @@ files.
 - <a id="opamfield-patches">`patches: [ <string> { <filter> } ... ]`</a>: a list
   of files relative to the project source root (often added through the `files/`
   metadata subdirectory). The listed patch files will be applied sequentially to
-  the source as with the `patch` command, stripping one level of leading
-  directories (`-p1`) -- which is what version control systems generally use .
-  Variable interpolation is available, so you can specify `patches: [ "file" ]`
-  to have the patch processed from `file.in`.
+  the source using the `patch` command (before opam 2.2) or `git apply`
+  (since opam 2.2), stripping one level of leading directories (`-p1`) -- which
+  is what version control systems generally use. Variable interpolation is
+  available, so you can specify `patches: [ "file" ]` to have the patch
+  processed from `file.in`.
 
     Patches may be applied conditionally by adding _filters_.
 

master_changes.md

@@ -152,3 +152,4 @@ users)
 
 ## opam-core
   * `OpamStd.Sys`: add `is_cygwin_variant_cygcheck` that returns true if in path `cygcheck` is from a Cygwin or MSYS2 installation [#5843 @rjbou]
+  * `OpamSystem.patch`: use `git -c core.autocrlf=false apply --unsafe-paths -p1 <patch>` instead of `patch` [#5400 @kit-ty-kate - fix #3433 #3782 #3639]