Changes between Version 12 and Version 13 of Tutorials/SubmittingPatch


Ignore:
Timestamp:
Jan 4, 2018, 6:59:05 PM (6 years ago)
Author:
jan vrany
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Tutorials/SubmittingPatch

    v12 v13  
    154154  2. Apply the patch:
    155155     {{{
    156      C:\prg_sdk\Stx-jv_branch_build\stx-jv\build\stx\libtool>hg import c:\prg_sdk\Stx-jv_branch_build\stx-    jv\build\patches\libtool_fix_2_of_2_rev_7c788008841c_Issue_99__Send_notification_to_services_also_from__basicWithoutRedraw___.patch
    157      }}}
     156     C:\prg_sdk\Stx-jv_branch_build\stx-jv\build\stx\libtool>hg import --no-commit c:\prg_sdk\Stx-jv_branch_build\stx-jv\build\patches\libtool_fix_2_of_2_rev_7c788008841c_Issue_99__Send_notification_to_services_also_from__basicWithoutRedraw___.patch
     157     }}}
     158     {{{
     159     #!div class="note"
     160     **Note:**
     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.
     162
     163     If you really want patches to be commited, please use `hg import --exact`.
     164     }}}
     165
     166     
    158167
    159168  3. Check if the patch is there