| 161 | | Please note the option `--no-commit` when importing patch(es) which only updates the working copy but does not commit. I changes were commited and the patch was wrong (or if it would be further improved) the you'd be left with some "old" commits and would have to get rid of them via `hg prune`. With `--no-commit` you an just `hg revert` them. |
| | 161 | Please note the option `--no-commit` when importing patch(es). It only updates the working copy but does not commit. |
| | 162 | |
| | 163 | If changes were committed and the patch proved to be wrong or it would need further improvement, then you'd be left with some "old" commits. You would then need to get rid of such "old" commits via `hg prune`. |
| | 164 | |
| | 165 | Using `--no-commit` option, saves you such tedious work, you need to run `hg revert` to dispose of them. |
