172 | | **Note2:** |
173 | | 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. |
174 | | |
175 | | The first step is, of course, natural `hg import --no-commit name1.patch`. |
176 | | |
177 | | 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. |
178 | | |
179 | | If you would like to use **powershell** then an option is to use `cat name2.patch | patch -p1` |
| 171 | **Note2:** |
| 172 | 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. |
| 173 | |
| 174 | The first step is, of course, natural `hg import --no-commit name1.patch`. |
| 175 | |
| 176 | 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. |
| 177 | |
| 178 | If you would like to use **powershell** then an option is to use `cat name2.patch | patch -p1`. |