Changes between Version 16 and Version 17 of Tutorials/SubmittingPatch

Timestamp:

Apr 24, 2018, 11:15:03 AM (6 years ago)

Author:

patrik.svestka@…

Comment:

adding information about subsequent patches to hg import --no-commit

Tutorials/SubmittingPatch

@@ -167 +167 @@
      If you really want patches to be committed, please use `hg import --exact`. 
      }}}
-
-     
-
-  3. Check if the patch is there
+     {{{
+     #!div class="note"
+     **Note2:**
+     Please note that if you want to test multiple patches (e.g. on Windows) with `--no-commit` it has to be done differently than `--no-commit` on subsequent steps.
+
+     The first step is, of course, natural `hg import --no-commit name1.patch`.  
+
+    During the second step you have use `patch.exe`.  It can be patched like this: `patch -p1 < name2.patch` (works only at **cmd.exe**!).  The `patch.exe` is from git e.g. `patch: /c/Program Files (x86)/Git/bin/patch.exe`) and with that one it works.
+
+    If you would like to use **powershell** then an option is to use `cat name2.patch | patch -p1`
+     }}}
+
+
+  3. Check if the patch is there (will not be shown when `--no-commit` is used)
      {{{
      C:\prg_sdk\Stx-jv_branch_build\stx-jv\build\stx\libtool>hg sum